From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: "Simon Horman" <horms@kernel.org>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Toke Høiland-Jørgensen" <toke@toke.dk>,
"Jiri Pirko" <jiri@resnulli.us>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
"Eric Dumazet" <edumazet@google.com>
Subject: [PATCH net 0/2] net/sched: sch_cake: annotate data-races in cake_dump_class_stats (series)
Date: Thu, 30 Apr 2026 06:16:08 +0000 [thread overview]
Message-ID: <20260430061610.3503483-1-edumazet@google.com> (raw)
cake_dump_class_stats() runs without qdisc spinlock being held.
In this series (of two), I add READ_ONCE()/WRITE_ONCE() annotations for:
- flow->head
- flow->dropped
- b->backlogs[]
- flow->deficit
- flow->cvars.dropping
- flow->cvars.count
- flow->cvars.p_drop
- flow->cvars.blue_timer
- flow->cvars.drop_next
Eric Dumazet (2):
net/sched: sch_cake: annotate data-races in cake_dump_class_stats (I)
net/sched: sch_cake: annotate data-races in cake_dump_class_stats (II)
net/sched/sch_cake.c | 155 +++++++++++++++++++++++--------------------
1 file changed, 83 insertions(+), 72 deletions(-)
--
2.54.0.545.g6539524ca2-goog
next reply other threads:[~2026-04-30 6:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 6:16 Eric Dumazet [this message]
2026-04-30 6:16 ` [PATCH net 1/2] net/sched: sch_cake: annotate data-races in cake_dump_class_stats (I) Eric Dumazet
2026-05-02 21:32 ` Toke Høiland-Jørgensen
2026-04-30 6:16 ` [PATCH net 2/2] net/sched: sch_cake: annotate data-races in cake_dump_class_stats (II) Eric Dumazet
2026-05-02 21:35 ` Toke Høiland-Jørgensen
2026-05-02 17:58 ` [PATCH net 0/2] net/sched: sch_cake: annotate data-races in cake_dump_class_stats (series) Simon Horman
2026-05-03 0: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=20260430061610.3503483-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.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=toke@toke.dk \
/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