linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Tommi Rantala <tommi.t.rantala@nokia.com>
Subject: [GIT PULL] devmem fix for v4.11-rc7
Date: Wed, 12 Apr 2017 11:54:22 -0700	[thread overview]
Message-ID: <20170412185422.GA49782@beast> (raw)

Hi,

Please pull this devmem change for v4.11-rc7. Tommi tested this successfully
and no one appears to have objected to the RFC patch, so here's the fix. :)

Thanks!

-Kees

The following changes since commit b9b3322f13f350587f17f0a76f008830e3a420d3:

  Merge branch 'stable-4.11' of git://git.infradead.org/users/pcmoore/audit (2017-04-12 00:02:33 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/devmem-v4.11-rc7

for you to fetch changes up to a4866aa812518ed1a37d8ea0c881dc946409de94:

  mm: Tighten x86 /dev/mem with zeroing reads (2017-04-12 11:40:23 -0700)

----------------------------------------------------------------
Fixes /dev/mem to read back zeros for System RAM areas in the 1MB exception
area on x86 to avoid exposing RAM or tripping hardened usercopy.

----------------------------------------------------------------
Kees Cook (1):
      mm: Tighten x86 /dev/mem with zeroing reads

 arch/x86/mm/init.c | 41 +++++++++++++++++++--------
 drivers/char/mem.c | 82 ++++++++++++++++++++++++++++++++++--------------------
 2 files changed, 82 insertions(+), 41 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-04-12 18:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170412185422.GA49782@beast \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tommi.t.rantala@nokia.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).