From: Matthew Wilcox <willy@infradead.org>
To: Kees Cook <keescook@chromium.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] usercopy: Skip HIGHMEM page checking
Date: Mon, 16 Sep 2019 17:32:09 -0700 [thread overview]
Message-ID: <20190917003209.GS29434@bombadil.infradead.org> (raw)
In-Reply-To: <201909161431.E69B29A0@keescook>
On Mon, Sep 16, 2019 at 02:32:56PM -0700, Kees Cook wrote:
> When running on a system with >512MB RAM with a 32-bit kernel built with:
>
> CONFIG_DEBUG_VIRTUAL=y
> CONFIG_HIGHMEM=y
> CONFIG_HARDENED_USERCOPY=y
>
> all execve()s will fail due to argv copying into kmap()ed pages, and on
> usercopy checking the calls ultimately of virt_to_page() will be looking
> for "bad" kmap (highmem) pointers due to CONFIG_DEBUG_VIRTUAL=y:
I don't understand why you want to skip the check. We must not cross a
page boundary of a kmapped page.
next prev parent reply other threads:[~2019-09-17 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:32 Kees Cook
2019-09-17 0:32 ` Matthew Wilcox [this message]
2019-09-17 3:05 ` Kees Cook
2019-09-17 16:36 ` Matthew Wilcox
2019-09-17 17:39 ` Kees Cook
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=20190917003209.GS29434@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@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