From: Sasha Levin <sashal@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Westphal <fw@strlen.de>,
stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 6.6.y 0/2] netfilter: fix catchall element double-free
Date: Wed, 22 Nov 2023 16:18:48 -0500 [thread overview]
Message-ID: <ZV5wOBdT2v58Hwiq@sashalap> (raw)
In-Reply-To: <ZV0jmKNgQpxCvf/R@calendula>
On Tue, Nov 21, 2023 at 10:39:54PM +0100, Pablo Neira Ayuso wrote:
>Hi Greg, Sasha,
>
>On Tue, Nov 21, 2023 at 01:14:20PM +0100, Florian Westphal wrote:
>> Hello,
>>
>> This series contains the backports of two related changes to fix
>> removal of timed-out catchall elements.
>>
>> As-is, removed element remains on the list and will be collected
>> again.
>>
>> The adjustments are needed because of missing commit
>> 0e1ea651c971 ("netfilter: nf_tables: shrink memory consumption of set elements"),
>> so we need to pass set_elem container struct instead of "elem_priv".
>
>Please, also apply this series to -stable 5.15, 6.1 and 6.5.
>
>This series apply cleanly to these -stable kernels, I have also tested
>this series on them.
>
>Tested-by: Pablo Neira Ayuso <pablo@netfilter.org>
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2023-11-22 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 12:14 [PATCH 6.6.y 0/2] netfilter: fix catchall element double-free Florian Westphal
2023-11-21 12:14 ` [PATCH 6.6.y 1/2] netfilter: nf_tables: remove catchall element in GC sync path Florian Westphal
2023-11-21 12:14 ` [PATCH 6.6.y 2/2] netfilter: nf_tables: split async and sync catchall in two functions Florian Westphal
2023-11-21 21:39 ` [PATCH 6.6.y 0/2] netfilter: fix catchall element double-free Pablo Neira Ayuso
2023-11-22 21:18 ` 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=ZV5wOBdT2v58Hwiq@sashalap \
--to=sashal@kernel.org \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.org \
--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 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).