From: Daniel Machon <daniel.machon@microchip.com>
To: Dudu Lu <phx0fer@gmail.com>
Cc: <jhs@mojatatu.com>, <jiri@resnulli.us>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net] net/sched: gred: keep the qdisc lock while updating the table
Date: Mon, 26 Oct 2026 08:52:44 +0100 [thread overview]
Message-ID: <20261026075244.txwwhh2vrolt7va4@DEN-DL-M70577> (raw)
In-Reply-To: <20261021155434.66572-1-phx0fer@gmail.com>
> gred_change_table_def() publishes table->DPs/def/red_flags under
> sch_tree_lock(), drops the lock, and then keeps writing state the
> datapath reads without it:
>
> - gred_enable_rio_mode()/gred_disable_rio_mode()/gred_disable_wred_mode()
> set/clear table->flags;
> - the red_flags_changed loop writes table->tab[i]->red_flags;
> - the shadowed-VQ loop frees table->tab[i] and clears the slot.
>
> gred_enqueue() and gred_dequeue() read those same fields (test_bit on
> table->flags, q->red_flags, t->tab[]/t->DPs) under the same root lock on
> another CPU, so the post-unlock writes race with the enqueue path:
>
> BUG: KCSAN: data-race in gred_change_table_def [sch_gred] / gred_enqueue [sch_gred]
> read (marked) to 0xffff000007ad3b00 of 8 bytes by task 110 on cpu 0:
> gred_enqueue+0x88/0xc60 [sch_gred]
> dev_qdisc_enqueue+0x4c/0x19c
> __dev_queue_xmit+0x10a4/0x1ea4
>
> The comment justifying the early unlock only covers the DP-vs-DPs check,
> which the shadowed-VQ free loop relies on; it does not cover the scalar
> mode bits and per-VQ red_flags written afterwards. Move the unlock below
> those updates so everything the datapath reads is published under the
> lock that protects it.
>
> Fixes: 6639607ed9de ("[PKT_SCHED]: GRED: Use a central table definition change procedure")
> Assisted-by: LLM
> Signed-off-by: Dudu Lu <phx0fer@gmail.com>
Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
next prev parent reply other threads:[~2026-10-26 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:54 [PATCH net] net/sched: gred: keep the qdisc lock while updating the table Dudu Lu
2026-10-23 10:57 ` Simon Horman
2026-10-26 7:52 ` Daniel Machon [this message]
2026-10-26 23:10 ` patchwork-bot+netdevbpf
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=20261026075244.txwwhh2vrolt7va4@DEN-DL-M70577 \
--to=daniel.machon@microchip.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=phx0fer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox