From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: stable <stable@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Kristian Evensen <kristian.evensen@gmail.com>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: ctnetlink: Resolve conntrack L3-protocol flush regression
Date: Tue, 28 May 2019 15:59:02 -0700 [thread overview]
Message-ID: <20190528225902.GA5989@kroah.com> (raw)
In-Reply-To: <6ad87483-711a-f205-8986-2217dab828d0@6wind.com>
On Tue, May 28, 2019 at 03:57:37PM +0200, Nicolas Dichtel wrote:
> Le 24/05/2019 à 11:22, Pablo Neira Ayuso a écrit :
> > On Mon, May 20, 2019 at 10:35:07AM +0200, Nicolas Dichtel wrote:
> >> Le 06/05/2019 à 15:16, Pablo Neira Ayuso a écrit :
> >>> On Mon, May 06, 2019 at 10:49:52AM +0200, Nicolas Dichtel wrote:
> >> [snip]
> >>>> Is it possible to queue this for stable?
> >>>
> >>> Sure, as soon as this hits Linus' tree.
> >>>
> >> FYI, it's now in Linus tree:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f8e608982022
> >
> > Please, send an email requesting this to stable@vger.kernel.org and
> > keep me on CC.
> This is a request to backport the upstream commit f8e608982022 ("netfilter:
> ctnetlink: Resolve conntrack L3-protocol flush regression") in stable trees.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-05-28 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 15:40 [PATCH] netfilter: ctnetlink: Resolve conntrack L3-protocol flush regression Kristian Evensen
2019-05-03 17:02 ` Nicolas Dichtel
2019-05-03 17:05 ` Pablo Neira Ayuso
2019-05-04 10:57 ` Kristian Evensen
2019-05-05 22:32 ` Pablo Neira Ayuso
2019-05-06 8:49 ` Nicolas Dichtel
2019-05-06 13:16 ` Pablo Neira Ayuso
2019-05-20 8:35 ` Nicolas Dichtel
2019-05-24 9:22 ` Pablo Neira Ayuso
2019-05-28 13:57 ` Nicolas Dichtel
2019-05-28 22:59 ` Greg KH [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=20190528225902.GA5989@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kristian.evensen@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pablo@netfilter.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.