From: Cong Wang <cwang@twopensource.com>
To: Xiangyu Lu <luxiangyu@huawei.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: Fri, 13 Jun 2014 10:04:19 -0700 [thread overview]
Message-ID: <CAHA+R7P8-Jw30h99PHhHw3G+Pe085VOtVo5h_noVHhZSV==BNA@mail.gmail.com> (raw)
In-Reply-To: <1402623070-26549-1-git-send-email-luxiangyu@huawei.com>
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.
next prev parent reply other threads:[~2014-06-13 17:05 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 ` Cong Wang [this message]
2014-06-16 10:19 ` [PATCH 0/5] Backport to 3.10.y for fix CVE-2014-0181 Xiangyu Lu
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='CAHA+R7P8-Jw30h99PHhHw3G+Pe085VOtVo5h_noVHhZSV==BNA@mail.gmail.com' \
--to=cwang@twopensource.com \
--cc=gregkh@linuxfoundation.org \
--cc=luxiangyu@huawei.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.