From: Xiangyu Lu <luxiangyu@huawei.com>
To: Cong Wang <cwang@twopensource.com>
Cc: <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/5] Backport to 3.10.y for fix CVE-2014-0181
Date: Mon, 16 Jun 2014 18:19:39 +0800 [thread overview]
Message-ID: <539EC4BB.7020305@huawei.com> (raw)
In-Reply-To: <CAHA+R7P8-Jw30h99PHhHw3G+Pe085VOtVo5h_noVHhZSV==BNA@mail.gmail.com>
On 2014/6/14 1:04, Cong Wang wrote:
> On Thu, Jun 12, 2014 at 6:31 PM, Xiangyu Lu <luxiangyu@huawei.com> wrote:
>> Hi Greg,
>> This backport fix CVE-2014-0181 which would still be vulnerable in
>> the latest 3.10.y, please add it.
> This is not how netdev works for stable. You need to check the
> FAQ:
>
> https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt
>
> Q: How can I tell what patches are queued up for backporting to the
> various stable releases?
>
> A: Normally Greg Kroah-Hartman collects stable commits himself, but
> for networking, Dave collects up patches he deems critical for the
> networking subsystem, and then hands them off to Greg.
>
OK, thanks! I will check it.
prev parent reply other threads:[~2014-06-16 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 1:31 [PATCH 0/5] Backport to 3.10.y for fix CVE-2014-0181 Xiangyu Lu
2014-06-13 1:31 ` [PATCH 1/5] netlink: Rename netlink_capable netlink_allowed Xiangyu Lu
2014-06-13 1:31 ` [PATCH 2/5] net: Move the permission check in sock_diag_put_filterinfo to packet_diag_dump Xiangyu Lu
2014-06-13 1:31 ` [PATCH 3/5] net: Add variants of capable for use on on sockets Xiangyu Lu
2014-06-13 1:31 ` [PATCH 4/5] net: Add variants of capable for use on netlink messages Xiangyu Lu
2014-06-13 1:31 ` [PATCH 5/5] net: Use netlink_ns_capable to verify the permisions of " Xiangyu Lu
2014-06-13 17:04 ` [PATCH 0/5] Backport to 3.10.y for fix CVE-2014-0181 Cong Wang
2014-06-16 10:19 ` Xiangyu Lu [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=539EC4BB.7020305@huawei.com \
--to=luxiangyu@huawei.com \
--cc=cwang@twopensource.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).