From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Salls <salls@cs.ucsb.edu>
Cc: linux-mm <linux-mm@kvack.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [PATCH] mm/mempolicy.c: fix error handling in set_mempolicy and mbind.
Date: Sat, 8 Apr 2017 10:59:19 -0700 [thread overview]
Message-ID: <CA+55aFxY=3AhkOAbDYgWHNrOaBP1q0efi2rWQBQ_Z3ZzUYH1+Q@mail.gmail.com> (raw)
In-Reply-To: <1491634091-18817-1-git-send-email-salls@cs.ucsb.edu>
On Fri, Apr 7, 2017 at 11:48 PM, Chris Salls <salls@cs.ucsb.edu> wrote:
> In the case that compat_get_bitmap fails we do not want to copy the
> bitmap to the user as it will contain uninitialized stack data and
> leak sensitive data.
Ack, looks sane, applied.
Linus
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-04-08 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 6:48 Chris Salls
2017-04-08 17:59 ` Linus Torvalds [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='CA+55aFxY=3AhkOAbDYgWHNrOaBP1q0efi2rWQBQ_Z3ZzUYH1+Q@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=salls@cs.ucsb.edu \
--cc=security@kernel.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