All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Matthew Wilcox <willy@infradead.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: [GIT PULL] usercopy fix for v5.4-rc1
Date: Thu, 26 Sep 2019 11:35:41 -0700	[thread overview]
Message-ID: <201909261131.65DA27B@keescook> (raw)

Hi Linus,

Please pull this usercopy fix for v5.4-rc1. Randy found a corner case
(HIGHMEM, DEBUG_VIRTUAL, >512MB RAM) with hardened usercopy that went
unnoticed since v4.8. This adds HIGHMEM awareness to hardened usercopy,
and has been living in -next for a bit more than a week now.

Thanks!

-Kees

The following changes since commit 4d856f72c10ecb060868ed10ff1b1453943fc6c8:

  Linux 5.3 (2019-09-15 14:19:32 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/usercopy-v5.4-rc1

for you to fetch changes up to 314eed30ede02fa925990f535652254b5bad6b65:

  usercopy: Avoid HIGHMEM pfn warning (2019-09-17 15:20:17 -0700)

----------------------------------------------------------------
Fix hardened usercopy under CONFIG_DEBUG_VIRTUAL

----------------------------------------------------------------
Kees Cook (1):
      usercopy: Avoid HIGHMEM pfn warning

 mm/usercopy.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

-- 
Kees Cook

             reply	other threads:[~2019-09-26 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26 18:35 Kees Cook [this message]
2019-09-26 20:10 ` [GIT PULL] usercopy fix for v5.4-rc1 pr-tracker-bot

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=201909261131.65DA27B@keescook \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.