From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, david.ward@ll.mit.edu, vega@nebusec.ai,
victor@mojatatu.com, zhanxusheng1024@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue
Date: Thu, 20 Aug 2026 20:40:13 +0000 [thread overview]
Message-ID: <178725841364.473641.6076100232757539064.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260818095927.15901-1-jhs@mojatatu.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 18 Aug 2026 05:59:27 -0400 you wrote:
> gred_enqueue(), bfifo_enqueue() and plug_enqueue() admit a packet when the
> current backlog plus the packet length fits within the queue limit:
>
> sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (gred default VQ)
> gred_backlog+qdisc_pkt_len(skb) <= q->limit (gred configured VQ)
> sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (bfifo)
> sch->qstats.backlog + skb->len <= q->limit (plug)
>
> [...]
Here is the summary with links:
- [net,v2] net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue
https://git.kernel.org/netdev/net/c/4c660ee8c809
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-20 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 9:59 [PATCH net v2] net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue Jamal Hadi Salim
2026-08-20 18:27 ` Simon Horman
2026-08-20 20:40 ` patchwork-bot+netdevbpf [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=178725841364.473641.6076100232757539064.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=david.ward@ll.mit.edu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vega@nebusec.ai \
--cc=victor@mojatatu.com \
--cc=zhanxusheng1024@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.