From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
netdev@vger.kernel.org, Brian Witte <brianwitte@mailfence.com>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
Konstantin Andreev <andreev@swemel.ru>
Subject: Re: [backport request] “netfilter: nf_tables: fix reset request deadlock” to LTS 6.18, 6.12
Date: Fri, 24 Jul 2026 07:22:34 -0400 [thread overview]
Message-ID: <20260724105500.stable-0002@kernel.org> (raw)
In-Reply-To: <07b303cd-03f1-4d0c-ae58-7439503247a5@swemel.ru>
> Please consider backporting the following series to LTS 6.18, 6.12
> (listed in the order of appearance in mainline)
>
> 779c60a5190c ("netfilter: nft_counter: serialize reset with spinlock")
> 30c4d7fb59ac ("netfilter: nft_quota: use atomic64_xchg for reset")
> 7f261bb906bf ("netfilter: nf_tables: revert commit_mutex usage in reset path")
Queued for 6.12 and 6.18, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-24 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 17:22 [backport request] “netfilter: nf_tables: fix reset request deadlock” to LTS 6.18, 6.12 Konstantin Andreev
2026-07-24 11:22 ` 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=20260724105500.stable-0002@kernel.org \
--to=sashal@kernel.org \
--cc=andreev@swemel.ru \
--cc=brianwitte@mailfence.com \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--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