From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Collins <bsderandrew@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: Missed stable line commit (upstream 859828c0ea476b42f3a93d69d117aaba90994b6f)
Date: Tue, 18 Nov 2014 17:19:33 -0800 [thread overview]
Message-ID: <20141119011933.GA22731@kroah.com> (raw)
In-Reply-To: <CAKTPYJQQprPnN1bUPxy32YREb8WARQztQYWL9-Qfhm6wLqbD0A@mail.gmail.com>
On Mon, Nov 03, 2014 at 03:11:01PM -0700, Andrew Collins wrote:
> I ran into an issue today on latest 3.10 stable line that looks to
> have been resolved upstream and tagged for stable:
>
> commit 859828c0ea476b42f3a93d69d117aaba90994b6f
> Author: Jiri Pirko <jiri@resnulli.us>
> Date: Thu Dec 5 16:27:37 2013 +0100
>
> br: fix use of ->rx_handler_data in code executed on non-rx_handler path
> ...
> Please apply to stable trees as well. Thanks.
>
> The commit did make it into the 3.12 stable line, but seems to have
> been missed in 3.10. The commit that causes the issue *did* make it
> into 3.10.16 so 3.10 is exposed to the issue:
>
> commit 960b8e5018a552f62cfbc0dfe94be7b6ba178f13
> Author: Hong Zhiguo <zhiguohong@tencent.com>
> Date: Sat Sep 14 22:42:28 2013 +0800
>
> bridge: fix NULL pointer deref of br_port_get_rcu
>
> [ Upstream commit 716ec052d2280d511e10e90ad54a86f5b5d4dcc2 ]
>
> Any chance 859828c0ea476b42f3a93d69d117aaba90994b6f could be pulled
> into the next 3.10 stable?
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2014-11-19 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 22:11 Missed stable line commit (upstream 859828c0ea476b42f3a93d69d117aaba90994b6f) Andrew Collins
2014-11-19 1:19 ` Greg KH [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=20141119011933.GA22731@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bsderandrew@gmail.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.