All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Alex Gartrell <alexgartrell@gmail.com>,
	Julian Anastasov <ja@ssi.bg>, Alex Gartrell <agartrell@fb.com>,
	lvs-devel@vger.kernel.org, netdev <netdev@vger.kernel.org>,
	kernel-team <kernel-team@fb.com>
Subject: Re: [PATCH,v2 net-next] ipvs: skb_orphan in case of forwarding
Date: Thu, 9 Jul 2015 09:29:27 +0900	[thread overview]
Message-ID: <20150709002925.GA24713@verge.net.au> (raw)
In-Reply-To: <1436390272.24939.10.camel@edumazet-glaptop2.roam.corp.google.com>

On Wed, Jul 08, 2015 at 11:17:52PM +0200, Eric Dumazet wrote:
> On Wed, 2015-07-08 at 13:56 -0700, Alex Gartrell wrote:
> > On Tue, Jul 7, 2015 at 6:33 PM, Simon Horman <horms@verge.net.au> wrote:
> > 
> > > Is there any possibility you could investigate which stable trees are
> > > effected by this bug?
> > 
> > Well this was certainly a problem in 3.10 (we had our own hacky
> > solution at the time) and every kernel since then would have also had
> > this problem.  I'm pretty sure this isn't a problem in 3.4 or before.
> > 
> 
> early demux was added in 3.6
> 
> Fixes: 41063e9dd119 ("ipv4: Early TCP socket demux.")

Thanks Eric, Thanks Alex,

I think things are as clear as they need to be.
I'll add the above Fixes tag and get things queued up.

      reply	other threads:[~2015-07-09  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 21:28 [PATCH,v2 net-next] ipvs: skb_orphan in case of forwarding Alex Gartrell
2015-07-05 21:28 ` Alex Gartrell
2015-07-05 22:13 ` Julian Anastasov
2015-07-05 22:19   ` Alex Gartrell
2015-07-06  3:50     ` Simon Horman
2015-07-06  4:14       ` Alex Gartrell
2015-07-08  1:33         ` Simon Horman
2015-07-08 20:56           ` Alex Gartrell
2015-07-08 21:17             ` Eric Dumazet
2015-07-09  0:29               ` Simon Horman [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=20150709002925.GA24713@verge.net.au \
    --to=horms@verge.net.au \
    --cc=agartrell@fb.com \
    --cc=alexgartrell@gmail.com \
    --cc=eric.dumazet@gmail.com \
    --cc=ja@ssi.bg \
    --cc=kernel-team@fb.com \
    --cc=lvs-devel@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.