From: Sasha Levin <sasha.levin@oracle.com>
To: Ani Sinha <ani@arista.com>, Eric Dumazet <eric.dumazet@gmail.com>
Cc: stable <stable@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context.
Date: Mon, 2 Nov 2015 22:48:59 -0500 [thread overview]
Message-ID: <56382EAB.8020602@oracle.com> (raw)
In-Reply-To: <CAOxq_8MKSV2QtTvFoEXXFjRFsFFaae_FUbPiZn2SZC9fwAEPeQ@mail.gmail.com>
On 11/02/2015 10:32 PM, Ani Sinha wrote:
> On Mon, Nov 2, 2015 at 4:50 PM, Eric Dumazet <eric.dumazet@gmail.com> 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
prev parent reply other threads:[~2015-11-03 3:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 0:40 [PATCH -stable 3.18, backport] ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in preemptible context Ani Sinha
2015-11-03 0:50 ` Eric Dumazet
2015-11-03 1:21 ` Ani Sinha
2015-11-03 3:32 ` Ani Sinha
2015-11-03 3:48 ` Sasha Levin [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=56382EAB.8020602@oracle.com \
--to=sasha.levin@oracle.com \
--cc=ani@arista.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@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 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).