From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>, netdev@vger.kernel.org
Cc: Zhan Xusheng <zhanxusheng@xiaomi.com>,
stable@vger.kernel.org, vega@nebusec.ai,
Victor Nogueira <victor@mojatatu.com>,
David Ward <david.ward@ll.mit.edu>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net] net: sched: gred: fix 32-bit backlog wrap in gred_enqueue
Date: Sun, 9 Aug 2026 17:43:24 +0800 [thread overview]
Message-ID: <20260809094325.2069096-1-zhanxusheng@xiaomi.com> (raw)
In-Reply-To: <20260809091657.879929-1-jhs@mojatatu.com>
On Sun, 9 Aug 2026 05:16:57 -0400, Jamal Hadi Salim wrote:
> - if (likely(sch->qstats.backlog + qdisc_pkt_len(skb) <=
> + if (likely((u64)sch->qstats.backlog + qdisc_pkt_len(skb) <=
> sch->limit))
bfifo_enqueue() in net/sched/sch_fifo.c has the same expression, and this
patch does not touch it:
if (likely(sch->qstats.backlog + qdisc_pkt_len(skb) <=
READ_ONCE(sch->limit)))
Same u32 backlog, same unsigned int length. sch->limit comes from
tc_fifo_qopt.limit, a __u32 documented as "bytes for bfifo", and nothing
caps it on the way in -- both .init and .change are fifo_init(), which
stores ctl->limit directly.
The gred check is the newer of the two: it came in with a3eb95f891d6,
the commit in your Fixes tag, while the bfifo one goes back to the
initial git import, so there is no useful Fixes: tag for it.
bfifo also has more ways in than gred. sch_red.c and sch_tbf.c install a
bfifo child through fifo_create_dflt() -> fifo_set_limit(), passing
ctl->limit and qopt->limit straight from userspace; tc_red_qopt.limit is
likewise documented as bytes. Since this is heading to stable, fixing
gred alone leaves those paths unchanged.
Minor, and in the other direction: __fifo_init() does
u32 limit = qdisc_dev(sch)->tx_queue_len;
if (is_bfifo)
limit *= psched_mtu(qdisc_dev(sch));
which also wraps in 32 bits, but fails safe -- the result stays below
2^32, so the limit ends up smaller than intended rather than unbounded.
Thanks,
Zhan Xusheng
next prev parent reply other threads:[~2026-08-09 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 9:16 [PATCH net] net: sched: gred: fix 32-bit backlog wrap in gred_enqueue Jamal Hadi Salim
2026-08-09 9:43 ` Zhan Xusheng [this message]
2026-08-09 9:56 ` Jamal Hadi Salim
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=20260809094325.2069096-1-zhanxusheng@xiaomi.com \
--to=zhanxusheng1024@gmail.com \
--cc=davem@davemloft.net \
--cc=david.ward@ll.mit.edu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--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=zhanxusheng@xiaomi.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