All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Alex Gartrell <alexgartrell@gmail.com>
Cc: 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: Wed, 8 Jul 2015 10:33:55 +0900	[thread overview]
Message-ID: <20150708013355.GE28100@verge.net.au> (raw)
In-Reply-To: <CALCkm3d4Xqq+eWryejKhi84rM_fS4QRyu8Fn_Z7RHZv+zbv3_Q@mail.gmail.com>

On Sun, Jul 05, 2015 at 09:14:38PM -0700, Alex Gartrell wrote:
> On Sun, Jul 5, 2015 at 8:50 PM, Simon Horman <horms@verge.net.au> wrote:
> > Is it possible to get a 'Fixes:' tag?
> 
> I suppose it'd be appropriate to say
> 
> Fixes: 41063e9dd119 ("ipv4: Early TCP socket demux.")
> 
> As that is what introduces tcp early_demux, but that's just a guess as
> I haven't bisected it (not even sure my test would run on that code
> base).

Thanks. The reason that I am asking about this is to ease getting
this fix, or a derivative of it, into the appropriate stable trees.

Is there any possibility you could investigate which stable trees are
effected by this bug?

  reply	other threads:[~2015-07-08  1:33 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 [this message]
2015-07-08 20:56           ` Alex Gartrell
2015-07-08 21:17             ` Eric Dumazet
2015-07-09  0:29               ` Simon Horman

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=20150708013355.GE28100@verge.net.au \
    --to=horms@verge.net.au \
    --cc=agartrell@fb.com \
    --cc=alexgartrell@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.