From: Greg KH <gregkh@linuxfoundation.org>
To: hujianyang <hujianyang@huawei.com>
Cc: stable@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
linux-ext4@vger.kernel.org, dmonakhov@openvz.org,
sasha.levin@oracle.com, tytso@mit.edu
Subject: Re: [PATCH][request for stable 3.10 inclusion] ext4 CVE-2014-8086
Date: Sat, 7 Feb 2015 16:51:56 +0800 [thread overview]
Message-ID: <20150207085156.GA20290@kroah.com> (raw)
In-Reply-To: <54D31F09.4010401@huawei.com>
On Thu, Feb 05, 2015 at 03:43:05PM +0800, hujianyang wrote:
> Hi Greg,
>
> The following patch commit a41537e69b4aa43f0fea02498c2595a81267383b
>
> ext4: prevent bugon on race between write/fcntl
>
> fix CVE-2014-8086 in upstream kernel. I wish you could merge this fix
> into stable 3.10. Since refactoring in ext4, the sending patch is quite
> different from the patch in upstream kernel.
Before I do that, can you also provide a backport to the 3.14-stable
kernel tree so that we don't have that tree missing this?
thanks,
greg k-h
next prev parent reply other threads:[~2015-02-07 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 7:43 [PATCH][request for stable 3.10 inclusion] ext4 CVE-2014-8086 hujianyang
2015-02-07 8:51 ` Greg KH [this message]
2015-02-07 8:54 ` Greg KH
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=20150207085156.GA20290@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmonakhov@openvz.org \
--cc=hujianyang@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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