Re: [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.

[Eric Dumazet]

On Mon, 2015-11-02 at 16:40 -0800, Ani Sinha wrote:
> [ Upstream commit 44f49dd8b5a606870a1f2 ] 

Please carefully read Documentation/networking/netdev-FAQ.txt

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.

   There is a patchworks queue that you can see here:
http://patchwork.ozlabs.org/bundle/davem/stable/?state=*

   It contains the patches which Dave has selected, but not yet handed
   off to Greg.  If Greg already has the patch, then it will be here:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git

   A quick way to find whether the patch is in this stable-queue is
   to simply clone the repo, and then git grep the mainline commit ID, e.g.

stable-queue$ git grep -l 284041ef21fdf2e
releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
stable/stable-queue$



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.

[Ani Sinha]

On Mon, Nov 2, 2015 at 4:50 PM, Eric Dumazet  wrote:
> On Mon, 2015-11-02 at 16:40 -0800, Ani Sinha wrote:
>> [ Upstream commit 44f49dd8b5a606870a1f2 ]
>
> Please carefully read Documentation/networking/netdev-FAQ.txt
>
> 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.
>
>There is a patchworks queue that you can see here:
> http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>
>It contains the patches which Dave has selected, but not yet handed
>off to Greg.  If Greg already has the patch, then it will be here:
> http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
>
>A quick way to find whether the patch is in this stable-queue is
>to simply clone the repo, and then git grep the mainline commit ID, e.g.
>
> stable-queue$ git grep -l 284041ef21fdf2e
> releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> stable/stable-queue$

Ah cool! Thanks for the pointer. Seems its already queued up for other
stable kernel version trains  :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.

[Sasha Levin]

On 11/02/2015 10:32 PM, Ani Sinha wrote:
> On Mon, Nov 2, 2015 at 4:50 PM, Eric Dumazet  wrote:
>> > On Mon, 2015-11-02 at 16:40 -0800, Ani Sinha wrote:
>>> >> [ Upstream commit 44f49dd8b5a606870a1f2 ]
>> >
>> > Please carefully read Documentation/networking/netdev-FAQ.txt
> I don't see any recent releases of 3.18 version series in Greg KH's
> tree. Is the 3.18 stable train being maintained by Sasha here?
> 
> http://git.kernel.org/cgit/linux/kernel/git/sashal/linux-stable.git/
> 
> If that is the case, should 3.18 specific backport patches be sent
> directly to him ?

The documentation is a bit lacking here. I follow the same procedure
as Greg: Dave sends us backports for patches he picks for -stable and
I apply them.

The only difference is that my (currently empty) queue is located elsewhere:
https://git.kernel.org/cgit/linux/kernel/git/sashal/linux-stable.git/log/?h=linux-3.18.y-queue

To sum it up, no need to send anything regarding -stable  net/ to anyone,
Dave does all the heavy lifting there (thanks Dave!).


Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.

[Ani Sinha]

On Mon, Nov 2, 2015 at 4:50 PM, Eric Dumazet  wrote:
> On Mon, 2015-11-02 at 16:40 -0800, Ani Sinha wrote:
>> [ Upstream commit 44f49dd8b5a606870a1f2 ]
>
> Please carefully read Documentation/networking/netdev-FAQ.txt

I don't see any recent releases of 3.18 version series in Greg KH's
tree. Is the 3.18 stable train being maintained by Sasha here?

http://git.kernel.org/cgit/linux/kernel/git/sashal/linux-stable.git/

If that is the case, should 3.18 specific backport patches be sent
directly to him ?

>
> 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.
>
>There is a patchworks queue that you can see here:
> http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
>
>It contains the patches which Dave has selected, but not yet handed
>off to Greg.  If Greg already has the patch, then it will be here:
> http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git
>
>A quick way to find whether the patch is in this stable-queue is
>to simply clone the repo, and then git grep the mainline commit ID, e.g.
>
> stable-queue$ git grep -l 284041ef21fdf2e
> releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch
> stable/stable-queue$
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html