From: Kuntal Nayak <kuntal.nayak@broadcom.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
ajay.kaher@broadcom.com, alexey.makhalov@broadcom.com,
vasavi.sirnapalli@broadcom.com, kadlec@netfilter.org,
fw@strlen.de, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6.1] netfilter: nf_tables: use timestamp to check for set element timeout
Date: Thu, 20 Jun 2024 11:49:41 -0700 [thread overview]
Message-ID: <CAA4K+2b6fAH2jKrxJGV8xHFupS6OkaJAFCtnZqjLvYXHNFA-Xw@mail.gmail.com> (raw)
In-Reply-To: <ZmmffoZAlP2wRQJL@calendula>
Hi Pablo,
Thank you for the update and reviewing the patch. We will wait for
your patch to be applied to the LTS and then consume the latest 6.1
kernel.
------
Best regards,
Kuntal
On Wed, Jun 12, 2024 at 6:15 AM Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
> Hi,
>
> Thanks for your patch.
>
> rbtree GC chunk is not correct though. In 6.1, GC runs via workqueue,
> so the cached timestamp cannot be used in such case.
>
> Another possibility is to pull in the patch dependency to run GC
> synchronously.
>
> I am preparing a batch of updates for -stable, let me pick up on your
> patch.
>
> Thanks.
>
> On Fri, Jun 07, 2024 at 04:01:46PM -0700, Kuntal Nayak wrote:
> > diff --git a/net/netfilter/nft_set_rbtree.c b/net/netfilter/nft_set_rbtree.c
> > index 5bf5572e9..c4c92192c 100644
> > --- a/net/netfilter/nft_set_rbtree.c
> > +++ b/net/netfilter/nft_set_rbtree.c
> [...]
> > @@ -622,12 +624,14 @@ static void nft_rbtree_gc(struct work_struct *work)
> > struct nft_set *set;
> > unsigned int gc_seq;
> > struct net *net;
> > + u64 tstamp;
> >
> > priv = container_of(work, struct nft_rbtree, gc_work.work);
> > set = nft_set_container_of(priv);
> > net = read_pnet(&set->net);
> > nft_net = nft_pernet(net);
> > gc_seq = READ_ONCE(nft_net->gc_seq);
> > + tstamp = nft_net_tstamp(net);
> >
> > if (nft_set_gc_is_pending(set))
> > goto done;
> > @@ -659,7 +663,7 @@ static void nft_rbtree_gc(struct work_struct *work)
> > rbe_end = rbe;
> > continue;
> > }
> > - if (!nft_set_elem_expired(&rbe->ext))
> > + if (!__nft_set_elem_expired(&rbe->ext, tstamp))
> > continue;
> >
> > nft_set_elem_dead(&rbe->ext);
> > --
> > 2.39.3
> >
prev parent reply other threads:[~2024-06-20 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 23:01 [PATCH v6.1] netfilter: nf_tables: use timestamp to check for set element timeout Kuntal Nayak
2024-06-12 13:15 ` Pablo Neira Ayuso
2024-06-20 18:49 ` Kuntal Nayak [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=CAA4K+2b6fAH2jKrxJGV8xHFupS6OkaJAFCtnZqjLvYXHNFA-Xw@mail.gmail.com \
--to=kuntal.nayak@broadcom.com \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.org \
--cc=vasavi.sirnapalli@broadcom.com \
/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).