From: Sasha Levin <sashal@kernel•org>
To: gregkh@linuxfoundation•org, stable@vger•kernel.org, pablo@netfilter•org
Cc: Sasha Levin <sashal@kernel•org>,
patches@lists•linux.dev, linux-kernel@vger•kernel.org,
kadlec@netfilter•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, horms@kernel•org,
netfilter-devel@vger•kernel.org, coreteam@netfilter•org,
netdev@vger•kernel.org, y0un9sa@gmail•com, fw@strlen•de,
Li hongliang <1468888505@139•com>
Subject: Re: [PATCH 6.6.y] netfilter: nf_tables: unconditionally bump set->nelems before insertion
Date: Tue, 19 May 2026 20:54:16 -0400 [thread overview]
Message-ID: <20260519220508.reply-0002@kernel.org> (raw)
In-Reply-To: <20260519075518.2106753-1-1468888505@139.com>
On Tue, May 19, 2026 at 03:55:18PM +0800, Li hongliang wrote:
> From: Pablo Neira Ayuso <pablo@netfilter•org>
>
> [ Upstream commit def602e498a4f951da95c95b1b8ce8ae68aa733a ]
>
> In case that the set is full, a new element gets published then removed
> without waiting for the RCU grace period, while RCU reader can be
> walking over it already.
[...]
> [ Minor conflict resolved. ]
> Signed-off-by: Li hongliang <1468888505@139•com>
Queued for 6.6, thanks.
Note: 6.1, 5.15 and 5.10 also contain the buggy Fixes: parent
(35d0ac9070ef) and would benefit from the same fix. A hand-crafted
backport for those branches would be welcome if you have the cycles.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-05-20 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:55 [PATCH 6.6.y] netfilter: nf_tables: unconditionally bump set->nelems before insertion Li hongliang
2026-05-20 0:54 ` Sasha Levin [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=20260519220508.reply-0002@kernel.org \
--to=sashal@kernel$(echo .)org \
--cc=1468888505@139$(echo .)com \
--cc=coreteam@netfilter$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=kadlec@netfilter$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=pablo@netfilter$(echo .)org \
--cc=patches@lists$(echo .)linux.dev \
--cc=stable@vger$(echo .)kernel.org \
--cc=y0un9sa@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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