From: Michael Marineau <michael.marineau@coreos.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Chuck Ebbert <cebbert.lkml@gmail.com>,
Shaun Crampton <Shaun.Crampton@metaswitch.com>,
linux-kernel@vger.kernel.org,
Peter White <Peter.White@metaswitch.com>,
netdev@vger.kernel.org
Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses
Date: Thu, 27 Aug 2015 09:32:37 -0700 [thread overview]
Message-ID: <CAGr1u3tSvD-d7CEOZ+d+BqZpkXkkmfrCduocCnX-jOmThfGnng@mail.gmail.com> (raw)
In-Reply-To: <1440693016.8932.41.camel@edumazet-glaptop2.roam.corp.google.com>
On Thu, Aug 27, 2015 at 9:30 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2015-08-27 at 09:16 -0700, Michael Marineau wrote:
>
>>
>> Oh, interesting. Looks like that patch didn't get CC'd to stable
>> though, is there a reason for that or just oversight?
>
> We never CC stable for networking patches.
>
> David Miller prefers to take care of this himself.
Ah, right, sorry. forgot about that. :)
>
> ( this is in 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.
>
> 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$
>
>
>
next prev parent reply other threads:[~2015-08-27 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 8:46 ip_rcv_finish() NULL pointer and possibly related Oopses Shaun Crampton
2015-08-26 11:49 ` Chuck Ebbert
2015-08-26 13:01 ` Shaun Crampton
2015-08-26 20:54 ` Michael Marineau
2015-08-27 13:00 ` Eric Dumazet
2015-08-27 16:16 ` Michael Marineau
2015-08-27 16:30 ` Eric Dumazet
2015-08-27 16:32 ` Michael Marineau [this message]
2015-08-27 16:40 ` David Miller
2015-08-27 16:47 ` Michael Marineau
2015-09-02 16:39 ` Shaun Crampton
2015-09-03 0:12 ` Daniel Borkmann
2015-09-03 8:13 ` Shaun Crampton
2015-09-03 9:03 ` Daniel Borkmann
2015-09-03 10:09 ` Shaun Crampton
2015-09-03 12:10 ` Eric Dumazet
2015-09-04 14:57 ` Shaun Crampton
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=CAGr1u3tSvD-d7CEOZ+d+BqZpkXkkmfrCduocCnX-jOmThfGnng@mail.gmail.com \
--to=michael.marineau@coreos.com \
--cc=Peter.White@metaswitch.com \
--cc=Shaun.Crampton@metaswitch.com \
--cc=cebbert.lkml@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.