From: David Miller <davem@davemloft.net>
To: michael.marineau@coreos.com
Cc: eric.dumazet@gmail.com, cebbert.lkml@gmail.com,
Shaun.Crampton@metaswitch.com, linux-kernel@vger.kernel.org,
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:40:11 -0700 (PDT) [thread overview]
Message-ID: <20150827.094011.2245604840519777428.davem@davemloft.net> (raw)
In-Reply-To: <CAGr1u3vDQDj6rJYcx2vCsf9KkWf-X=qSh3QD-jAZf7hpUYaAyg@mail.gmail.com>
From: Michael Marineau <michael.marineau@coreos.com>
Date: Thu, 27 Aug 2015 09:16:06 -0700
> On Thu, Aug 27, 2015 at 6:00 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> Make sure you backported commit
>> 10e2eb878f3ca07ac2f05fa5ca5e6c4c9174a27a
>> ("udp: fix dst races with multicast early demux")
>
> Oh, interesting. Looks like that patch didn't get CC'd to stable
> though, is there a reason for that or just oversight?
All networking bug fixes are submitted to -stable by hand by me at a
time of my choosing. We do not use the "CC: stable" facility, as I
feel it pushes patches into -stable way too quickly and before the
change gets sufficient exposure for regressions in Linus's tree.
The patch in question got submitted last night.
next prev parent reply other threads:[~2015-08-27 16:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D2033B8F.4133C%Shaun.Crampton@metaswitch.com>
2015-08-26 11:49 ` ip_rcv_finish() NULL pointer and possibly related Oopses 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
2015-08-27 16:40 ` David Miller [this message]
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=20150827.094011.2245604840519777428.davem@davemloft.net \
--to=davem@davemloft.net \
--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=michael.marineau@coreos.com \
--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 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).