From: Kees Cook <keescook@chromium.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: linux-mm@kvack.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] Assorted improvements to usercopy
Date: Tue, 5 Oct 2021 14:27:46 -0700 [thread overview]
Message-ID: <202110051426.11E5102F6@keescook> (raw)
In-Reply-To: <20211004224224.4137992-1-willy@infradead.org>
On Mon, Oct 04, 2021 at 11:42:20PM +0100, Matthew Wilcox (Oracle) wrote:
> We must prohibit page boundary crossing for kmap() addresses.
> vmap() addresses are limited by the length of the mapping, and
> compound pages are limited by the size of the page.
>
> These should probably all have test cases?
>
> Matthew Wilcox (Oracle) (3):
> mm/usercopy: Check kmap addresses properly
> mm/usercopy: Detect vmalloc overruns
> mm/usercopy: Detect compound page overruns
Thanks! This is a nice additional bit of checking. I wonder if the CMA
and Reserved pieces should be extracted from the PAGESPAN check too?
Probably that CONFIG should be renamed as well now. :P
-Kees
>
> arch/x86/include/asm/highmem.h | 1 +
> include/linux/highmem-internal.h | 10 ++++++++++
> mm/usercopy.c | 33 +++++++++++++++++++++-----------
> 3 files changed, 33 insertions(+), 11 deletions(-)
>
> --
> 2.32.0
>
--
Kees Cook
prev parent reply other threads:[~2021-10-05 21:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 22:42 Matthew Wilcox (Oracle)
2021-10-04 22:42 ` [PATCH 1/3] mm/usercopy: Check kmap addresses properly Matthew Wilcox (Oracle)
2021-10-05 21:23 ` Kees Cook
2021-10-05 21:43 ` Matthew Wilcox
2021-10-05 21:54 ` Kees Cook
2021-10-04 22:42 ` [PATCH 2/3] mm/usercopy: Detect vmalloc overruns Matthew Wilcox (Oracle)
2021-10-05 21:25 ` Kees Cook
2021-10-06 1:26 ` Matthew Wilcox
2021-10-06 3:02 ` Kees Cook
2021-10-04 22:42 ` [PATCH 3/3] mm/usercopy: Detect compound page overruns Matthew Wilcox (Oracle)
2021-10-05 21:26 ` Kees Cook
2021-10-05 22:12 ` Matthew Wilcox
2021-10-05 22:55 ` Kees Cook
2021-10-05 21:27 ` Kees Cook [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202110051426.11E5102F6@keescook \
--to=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox