From: Kees Cook <keescook@chromium.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2 3/3] mm/usercopy: Detect compound page overruns
Date: Wed, 6 Oct 2021 15:07:40 -0700 [thread overview]
Message-ID: <202110061506.CF5BDD0@keescook> (raw)
In-Reply-To: <YV2t7q7nnOFHexUz@casper.infradead.org>
On Wed, Oct 06, 2021 at 03:08:46PM +0100, Matthew Wilcox wrote:
> On Wed, Oct 06, 2021 at 01:42:26PM +0100, Matthew Wilcox (Oracle) wrote:
> > Move the compound page overrun detection out of
> > CONFIG_HARDENED_USERCOPY_PAGESPAN so it's enabled for more people.
> >
> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> > Acked-by: Kees Cook <keescook@chromium.org>
> > ---
> > mm/usercopy.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/mm/usercopy.c b/mm/usercopy.c
> > index 63476e1506e0..b825c4344917 100644
> > --- a/mm/usercopy.c
> > +++ b/mm/usercopy.c
> > @@ -194,11 +194,6 @@ static inline void check_page_span(const void *ptr, unsigned long n,
> > ((unsigned long)end & (unsigned long)PAGE_MASK)))
> > return;
> >
> > - /* Allow if fully inside the same compound (__GFP_COMP) page. */
> > - endpage = virt_to_head_page(end);
> > - if (likely(endpage == page))
> > - return;
> > -
> > /*
> > * Reject if range is entirely either Reserved (i.e. special or
> > * device memory), or CMA. Otherwise, reject since the object spans
>
> Needs an extra hunk to avoid a warning with that config:
Ah yeah, good catch.
>
> @@ -163,7 +163,6 @@ static inline void check_page_span(const void *ptr, unsigned long n,
> {
> #ifdef CONFIG_HARDENED_USERCOPY_PAGESPAN
> const void *end = ptr + n - 1;
> - struct page *endpage;
> bool is_reserved, is_cma;
>
> /*
>
> I'll wait a few days and send a v3.
When you send v3, can you CC linux-hardening@vger.kernel.org too?
Thanks for poking at this!
-Kees
--
Kees Cook
prev parent reply other threads:[~2021-10-06 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 12:42 [PATCH v2 0/3] Assorted improvements to usercopy Matthew Wilcox (Oracle)
2021-10-06 12:42 ` [PATCH v2 1/3] mm/usercopy: Check kmap addresses properly Matthew Wilcox (Oracle)
2021-10-06 12:42 ` [PATCH v2 2/3] mm/usercopy: Detect vmalloc overruns Matthew Wilcox (Oracle)
2021-10-06 12:42 ` [PATCH v2 3/3] mm/usercopy: Detect compound page overruns Matthew Wilcox (Oracle)
2021-10-06 14:08 ` Matthew Wilcox
2021-10-06 22:07 ` 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=202110061506.CF5BDD0@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