linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uaccess: Disallow > INT_MAX copy sizes
Date: Tue, 24 Sep 2019 16:29:59 -0700	[thread overview]
Message-ID: <20190924162959.25ccaac45dec9a8697e1ca27@linux-foundation.org> (raw)
In-Reply-To: <201909231607.B6A0736@keescook>

On Mon, 23 Sep 2019 16:08:54 -0700 Kees Cook <keescook@chromium.org> wrote:

> On Sun, Aug 25, 2019 at 04:18:56PM -0700, Kees Cook wrote:
> > As we've done with VFS, string operations, etc, reject usercopy sizes
> > larger than INT_MAX, which would be nice to have for catching bugs
> > related to size calculation overflows[1].
> > 
> > This adds 10 bytes to x86_64 defconfig text and 1980 bytes to the data
> > section:
> > 
> >    text    data     bss     dec     hex filename
> > 19691167        5134320 1646664 26472151        193eed7 vmlinux.before
> > 19691177        5136300 1646664 26474141        193f69d vmlinux.after
> > 
> > [1] https://marc.info/?l=linux-s390&m=156631939010493&w=2
> > 
> > Suggested-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> ping! Andrew, can you take this?

It's in my post 5.4-rc1 pile.

      reply	other threads:[~2019-09-24 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25 23:18 [PATCH] uaccess: Disallow > INT_MAX copy sizes Kees Cook
2019-09-23 23:08 ` Kees Cook
2019-09-24 23:29   ` Andrew Morton [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=20190924162959.25ccaac45dec9a8697e1ca27@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).