From: Zhongqiu Duan <dzq.aishenghu0@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Zhongqiu Duan <dzq.aishenghu0@gmail.com>,
coreteam@netfilter.org, netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH nf] netfilter: nft_quota: make nft_overquota() really over the quota
Date: Thu, 17 Apr 2025 15:31:10 +0000 [thread overview]
Message-ID: <aAEamcS1xBIGfJ1i@fire> (raw)
In-Reply-To: <aADkVkvVHlCpw061@calendula>
On Thu, Apr 17, 2025 at 01:21:58PM +0200, Pablo Neira Ayuso wrote:
> Hi,
>
> On Tue, Apr 15, 2025 at 02:03:59PM +0000, Zhongqiu Duan wrote:
> [...]
> > They behave differently in the case of consumed bytes equal to quota.
> >
> > From nft_quota:
> >
> > overquota = nft_overquota(priv, pkt->skb);
> > if (overquota ^ nft_quota_invert(priv))
> > regs->verdict.code = NFT_BREAK;
> >
> > The xt_quota compares skb length with remaining quota, but the nft_quota
> > compares it with consumed bytes.
> >
> > The xt_quota can match consumed bytes up to quota at maximum. But the
> > nft_quota break match when consumed bytes equal to quota.
> >
> > i.e., nft_quota match consumed bytes in [0, quota - 1], not [0, quota].
>
> Thanks for explaining.
>
> > Also note that after applying this patch, nft_quota obj will report when
> > consumed bytes exceed the quota, but nfacct can report when consumed
> > bytes are greater than or equal to the quota.
> >
> > From nft_quota:
> >
> > if (overquota &&
> > !test_and_set_bit(NFT_QUOTA_DEPLETED_BIT, &priv->flags))
> > nft_obj_notify(...);
> >
> > From nfacct:
> >
> > if (now >= *quota &&
> > !test_and_set_bit(NFACCT_OVERQUOTA_BIT, &nfacct->flags)) {
> > nfnl_overquota_report(net, nfacct);
> > }
> >
> > Should we report when quota is exhausted but not exceeded?
>
> I think it is good if nfacct and nft_quota behave in the same way.
>
> I'd suggest you collapse this patch.
>
> Please, route this patch v2 through the nf-next tree.
>
Okay, I will send v2 to the nf-next tree.
Thanks for your attention.
> Thanks.
> diff --git a/net/netfilter/nft_quota.c b/net/netfilter/nft_quota.c
> index 0bb43c723061..9fd6985f54c5 100644
> --- a/net/netfilter/nft_quota.c
> +++ b/net/netfilter/nft_quota.c
> @@ -51,13 +51,15 @@ static void nft_quota_obj_eval(struct nft_object *obj,
> const struct nft_pktinfo *pkt)
> {
> struct nft_quota *priv = nft_obj_data(obj);
> + u64 consumed = atomic64_add_return(pkt->skb->len, priv->consumed);
> + u64 quota = atomic64_read(&priv->quota);
> bool overquota;
>
> - overquota = nft_overquota(priv, pkt->skb);
> + overquota = (consumed > quota);
> if (overquota ^ nft_quota_invert(priv))
> regs->verdict.code = NFT_BREAK;
>
> - if (overquota &&
> + if (consumed >= quota &&
> !test_and_set_bit(NFT_QUOTA_DEPLETED_BIT, &priv->flags))
> nft_obj_notify(nft_net(pkt), obj->key.table, obj, 0, 0,
> NFT_MSG_NEWOBJ, 0, nft_pf(pkt), 0, GFP_ATOMIC);
prev parent reply other threads:[~2025-04-17 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 7:17 [PATCH nf] netfilter: nft_quota: make nft_overquota() really over the quota Zhongqiu Duan
2025-04-14 21:55 ` Pablo Neira Ayuso
2025-04-15 14:03 ` Zhongqiu Duan
2025-04-17 11:21 ` Pablo Neira Ayuso
2025-04-17 15:31 ` Zhongqiu Duan [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=aAEamcS1xBIGfJ1i@fire \
--to=dzq.aishenghu0@gmail.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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