From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [PATCH v2] vfs: read file_handle only once in handle_to_path
Date: Tue, 2 Jun 2015 10:23:42 -0700 [thread overview]
Message-ID: <CA+55aFwdwBQ0sTP4me6Ys_8gLKP3A5PbkFapYwcny10ByoeeDw@mail.gmail.com> (raw)
In-Reply-To: <556DCA77.2040001@oracle.com>
On Tue, Jun 2, 2015 at 8:23 AM, Sasha Levin <sasha.levin@oracle.com> wrote:
>
> This commit fixes a race condition an unprivileged user can exploit to corrupt
> kernel memory. I can't seem to get anyone to grab it for the past 4+ months.
Will take it directly. Feel free to just cc me directly earlier if
things take this long.
Thanks,
Linus
prev parent reply other threads:[~2015-06-02 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 20:30 [PATCH v2] vfs: read file_handle only once in handle_to_path Sasha Levin
2015-04-30 15:04 ` Sasha Levin
2015-06-02 15:23 ` Sasha Levin
2015-06-02 17:23 ` 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+55aFwdwBQ0sTP4me6Ys_8gLKP3A5PbkFapYwcny10ByoeeDw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=security@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).