From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable <stable@vger.kernel.org>
Subject: Re: netfilter/x_tables patches for v4.4.y..v4.14.y
Date: Thu, 15 Apr 2021 10:54:17 -0700 [thread overview]
Message-ID: <20210415175417.GA30883@roeck-us.net> (raw)
In-Reply-To: <20210415174950.GB30478@roeck-us.net>
On Thu, Apr 15, 2021 at 10:49:50AM -0700, Guenter Roeck wrote:
> On Thu, Apr 15, 2021 at 06:37:41PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Apr 15, 2021 at 09:28:15AM -0700, Guenter Roeck wrote:
> > > Hi Greg,
> > >
> > > please consider applying the following two patches to v4.4.y, v4.9.y, and v4.14.y
> > >
> > > 80055dab5de0 ("netfilter: x_tables: make xt_replace_table wait until old rules are not used anymore")
> > > 175e476b8cdf ("netfilter: x_tables: Use correct memory barriers.")
> >
> > The second patch here says that it's only needed to go back until:
> > Fixes: 7f5c6d4f665b ("netfilter: get rid of atomic ops in fast path")
> >
> > Which is only backported to 4.19. So why do older kernels need that, is
> > the fixes tag wrong?
> >
>
> Outch, it looks like 80055dab5de0 was fixed later with cc00bcaa5899, which in
> turn was fixed with 443d6e86f821. Ok, back to the drawing board, but it may
> just be easier to forget about this. I'll let you know.
>
I tried to apply cc00bcaa5899 on top of the above, and got lots of conflicts.
Please ignore this request; it adds more risk than gain. Sorry for the noise.
Guenter
next prev parent reply other threads:[~2021-04-15 17:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 16:28 netfilter/x_tables patches for v4.4.y..v4.14.y Guenter Roeck
2021-04-15 16:37 ` Greg Kroah-Hartman
2021-04-15 17:41 ` Guenter Roeck
2021-04-16 5:21 ` Greg Kroah-Hartman
2021-04-16 5:25 ` Guenter Roeck
2021-04-15 17:49 ` Guenter Roeck
2021-04-15 17:54 ` Guenter Roeck [this message]
2021-04-16 5:21 ` Greg Kroah-Hartman
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=20210415175417.GA30883@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.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).