From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
kadlec@netfilter.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: Patch "netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type" has been added to the 6.9-stable tree
Date: Sun, 23 Jun 2024 23:57:53 +0200 [thread overview]
Message-ID: <ZniaYe9C8Ys_2IfM@calendula> (raw)
In-Reply-To: <2024061900-precise-underuse-d4f4@gregkh>
Hi Greg,
On Wed, Jun 19, 2024 at 12:57:15PM +0200, Greg KH wrote:
> On Mon, Jun 17, 2024 at 03:04:50PM +0200, Pablo Neira Ayuso wrote:
> > Hi Sasha,
> >
> > This fix requires a follow up to silence a RCU suspicious usage warning.
> >
> > Please, hold on until end of the week with this.
> >
> > I will get back to you with a reminder if it helps.
>
> Dropped from all queues, please resend it when you feel it is ready to
> be added.
commit 8ecd06277a7664f4ef018abae3abd3451d64e7a6
Author: Jozsef Kadlecsik <kadlec@netfilter.org>
Date: Mon Jun 17 11:18:15 2024 +0200
netfilter: ipset: Fix suspicious rcu_dereference_protected()
is now upstream, which provides the incremental fix for:
commit 4e7aaa6b82d63e8ddcbfb56b4fd3d014ca586f10
Author: Jozsef Kadlecsik <kadlec@netfilter.org>
Date: Tue Jun 4 15:58:03 2024 +0200
netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type
These two patches can now be queued up to -stable.
Thanks
prev parent reply other threads:[~2024-06-23 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240617113341.2561910-1-sashal@kernel.org>
2024-06-17 13:04 ` Patch "netfilter: ipset: Fix race between namespace cleanup and gc in the list:set type" has been added to the 6.9-stable tree Pablo Neira Ayuso
2024-06-19 10:57 ` Greg KH
2024-06-23 21:57 ` Pablo Neira Ayuso [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=ZniaYe9C8Ys_2IfM@calendula \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.com \
--cc=sashal@kernel.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).