From: Sasha Levin <sashal@kernel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, kuntal.nayak@broadcom.com,
stable@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH -stable,6.1.x] netfilter: nf_tables: use timestamp to check for set element timeout
Date: Thu, 27 Jun 2024 16:04:25 -0400 [thread overview]
Message-ID: <Zn3FyYTUl267N1t_@sashalap> (raw)
In-Reply-To: <20240626235314.281432-1-pablo@netfilter.org>
On Thu, Jun 27, 2024 at 01:53:13AM +0200, Pablo Neira Ayuso wrote:
>commit 7395dfacfff65e9938ac0889dafa1ab01e987d15 upstream
>
>Add a timestamp field at the beginning of the transaction, store it
>in the nftables per-netns area.
>
>Update set backend .insert, .deactivate and sync gc path to use the
>timestamp, this avoids that an element expires while control plane
>transaction is still unfinished.
>
>.lookup and .update, which are used from packet path, still use the
>current time to check if the element has expired. And .get path and dump
>also since this runs lockless under rcu read size lock. Then, there is
>async gc which also needs to check the current time since it runs
>asynchronously from a workqueue.
>
>Fixes: c3e1b005ed1c ("netfilter: nf_tables: add set element timeout support")
>Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>---
>This is a backport for 6.1.x, please apply.
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2024-06-27 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 23:53 [PATCH -stable,6.1.x] netfilter: nf_tables: use timestamp to check for set element timeout Pablo Neira Ayuso
2024-06-27 20:04 ` 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=Zn3FyYTUl267N1t_@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuntal.nayak@broadcom.com \
--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