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, Vinson Lee <vlee@freedesktop.org>
Subject: [GIT PULL] usercopy fixes for v4.8-rc6-part2
Date: Wed, 7 Sep 2016 11:36:47 -0700	[thread overview]
Message-ID: <20160907183646.GA1270@www.outflux.net> (raw)

Hi,

Please pull these usercopy fixes for v4.8-rc6-part2.

Thanks!

-Kees

The following changes since commit ab29b33a84f6910ebf01a32f69a370886a4283dd:

  Merge tag 'seccomp-v4.8-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2016-09-07 10:46:06 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/usercopy-v4.8-rc6-part2

for you to fetch changes up to 8e1f74ea02cf4562404c48c6882214821552c13f:

  usercopy: remove page-spanning test for now (2016-09-07 11:33:26 -0700)

----------------------------------------------------------------
- force check_object_size() to be inline too
- move page-spanning check behind a CONFIG since it's triggering false positives

----------------------------------------------------------------
Kees Cook (2):
      usercopy: force check_object_size() inline
      usercopy: remove page-spanning test for now

 include/linux/thread_info.h |  4 +--
 mm/usercopy.c               | 61 ++++++++++++++++++++++++++-------------------
 security/Kconfig            | 11 ++++++++
 3 files changed, 48 insertions(+), 28 deletions(-)

-- 
Kees Cook
Nexus Security

             reply	other threads:[~2016-09-07 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 18:36 Kees Cook [this message]
2016-09-07 19:15 ` [GIT PULL] usercopy fixes for v4.8-rc6-part2 Linus Torvalds
2016-09-07 21:32   ` Kees Cook
2016-09-07 21:48     ` 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=20160907183646.GA1270@www.outflux.net \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vlee@freedesktop.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).