From: Greg KH <gregkh@linuxfoundation.org>
To: Florian Westphal <fw@strlen.de>
Cc: alexander.levin@microsoft.com, pablo@netfilter.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "netfilter: core: only allow one nat hook per hook point" has been added to the 4.15-stable tree
Date: Mon, 9 Apr 2018 13:51:01 +0200 [thread overview]
Message-ID: <20180409115101.GB22354@kroah.com> (raw)
In-Reply-To: <20180409094728.65iolgzplkcqi3if@breakpoint.cc>
On Mon, Apr 09, 2018 at 11:47:28AM +0200, Florian Westphal wrote:
> gregkh@linuxfoundation.org <gregkh@linuxfoundation.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > netfilter: core: only allow one nat hook per hook point
> >
> > to the 4.15-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > netfilter-core-only-allow-one-nat-hook-per-hook-point.patch
> > and it can be found in the queue-4.15 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> >
> > From foo@baz Mon Apr 9 10:16:32 CEST 2018
> > From: Florian Westphal <fw@strlen.de>
> > Date: Fri, 8 Dec 2017 17:01:54 +0100
> > Subject: netfilter: core: only allow one nat hook per hook point
> >
> > From: Florian Westphal <fw@strlen.de>
>
> NAK.
>
> This also needs
> netfilter: nf_tables: permit second nat hook if colliding hook is going away
>
> I would not add these to stable.
Thank you for letting me know, now dropped from my tree.
greg k-h
prev parent reply other threads:[~2018-04-09 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 9:36 Patch "netfilter: core: only allow one nat hook per hook point" has been added to the 4.15-stable tree gregkh
2018-04-09 9:47 ` Florian Westphal
2018-04-09 11:51 ` 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=20180409115101.GB22354@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=fw@strlen.de \
--cc=pablo@netfilter.org \
--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 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).