All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: pespin.shar@gmail.com, lorenzo@google.com,
	pau.espin@tessares.net, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "tcp: fix mark propagation with fwmark_reflect enabled" has been added to the 4.4-stable tree
Date: Thu, 16 Feb 2017 11:51:29 -0800	[thread overview]
Message-ID: <20170216195129.GB30382@kroah.com> (raw)
In-Reply-To: <20170216190141.GA18589@salvia>

On Thu, Feb 16, 2017 at 08:01:41PM +0100, Pablo Neira Ayuso wrote:
> Hi Greg,
> 
> if you pick this one, then you take this one as well:
> 
> commit 92e55f412cffd016cc245a74278cb4d7b89bb3bc
> Author: Pablo Neira <pablo@netfilter.org>
> Date:   Thu Jan 26 22:56:21 2017 +0100
> 
>     tcp: don't annotate mark on control socket from tcp_v6_send_response()
> 
> Since the IPv6 chunk is broken.

Ugh, that doesn't apply at all to 4.4-stable. Should I just drop this
patch from the 4.4-stable tree, or do you want to backport this for me?

also, I think there are a number of netfilter patches I should be
applying to the stable releases, specifically stuff like e5072053b096
("netfilter: conntrack: refine gc worker heuristics, redux")

Any ideas of things I should be applying?  Or should I just not worry
about this?  :)

thanks,

greg k-h

  reply	other threads:[~2017-02-16 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 17:05 Patch "tcp: fix mark propagation with fwmark_reflect enabled" has been added to the 4.4-stable tree gregkh
2017-02-16 19:01 ` Pablo Neira Ayuso
2017-02-16 19:51   ` Greg KH [this message]
2017-02-18 15:42 gregkh

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=20170216195129.GB30382@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=lorenzo@google.com \
    --cc=pablo@netfilter.org \
    --cc=pau.espin@tessares.net \
    --cc=pespin.shar@gmail.com \
    --cc=stable-commits@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 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.