From: Xiang Mei <xmei5@asu.edu>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: netdev@vger.kernel.org
Subject: Re: [bug report] net/sched: sch_qfq: Fix race condition on qfq_aggregate
Date: Thu, 17 Jul 2025 13:06:15 -0700 [thread overview]
Message-ID: <aHlXt3HBd--0JGqZ@xps> (raw)
In-Reply-To: <4a04e0cc-a64b-44e7-9213-2880ed641d77@sabinyo.mountain>
On Thu, Jul 17, 2025 at 11:51:43AM -0500, Dan Carpenter wrote:
> Hello Xiang Mei,
>
> Commit 5e28d5a3f774 ("net/sched: sch_qfq: Fix race condition on
> qfq_aggregate") from Jul 10, 2025 (linux-next), leads to the
> following Smatch static checker warning:
>
> net/sched/sch_generic.c:1107 qdisc_put()
> warn: sleeping in atomic context
>
> 547 static int qfq_delete_class(struct Qdisc *sch, unsigned long arg,
> 548 struct netlink_ext_ack *extack)
> 549 {
> 550 struct qfq_sched *q = qdisc_priv(sch);
> 551 struct qfq_class *cl = (struct qfq_class *)arg;
> 552
> 553 if (qdisc_class_in_use(&cl->common)) {
> 554 NL_SET_ERR_MSG_MOD(extack, "QFQ class in use");
> 555 return -EBUSY;
> 556 }
> 557
> 558 sch_tree_lock(sch);
> 559
> 560 qdisc_purge_queue(cl->qdisc);
> 561 qdisc_class_hash_remove(&q->clhash, &cl->common);
> 562 qfq_destroy_class(sch, cl);
> ^^^^^^^^^^^^^^^^^
> We used to unlock first and then did the destroy but the patch moved
> this qfq_destroy_class() under the sch_tree_unlock() to solve a race
> condition. Unfortunately, it introduces a sleeping in atomic context.
>
> 563
> 564 sch_tree_unlock(sch);
> 565
> 566 return 0;
> 567 }
>
> The call tree is:
>
> qfq_delete_class() <- disables preempt
> -> qfq_destroy_class()
> -> qdisc_put() <- sleeps
>
> net/sched/sch_generic.c
> 1098 void qdisc_put(struct Qdisc *qdisc)
> 1099 {
> 1100 if (!qdisc)
> 1101 return;
> 1102
> 1103 if (qdisc->flags & TCQ_F_BUILTIN ||
> 1104 !refcount_dec_and_test(&qdisc->refcnt))
> 1105 return;
> 1106
> --> 1107 __qdisc_destroy(qdisc);
>
> It's the lockdep_unregister_key() call which sleeps.
>
> 1108 }
>
> regards,
> dan carpenter
Thanks Dan for the explanations.
What do you think about this solution: We split qfq_destory_class to two
parts: qfq_rm_from_agg(q, cl) and the left calls. Since the race condition
is about agg, we can keep the left calls out of the lock but moving
qfq_rm_from_agg into the lock.
This could avoid calling __qdisc_destroy in the lock. Please let me know
if it works, I can help to deliever a new version of patch.
Best,
Xiang
next prev parent reply other threads:[~2025-07-17 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 16:51 [bug report] net/sched: sch_qfq: Fix race condition on qfq_aggregate Dan Carpenter
2025-07-17 20:06 ` Xiang Mei [this message]
2025-07-17 20:44 ` Dan Carpenter
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=aHlXt3HBd--0JGqZ@xps \
--to=xmei5@asu.edu \
--cc=dan.carpenter@linaro.org \
--cc=netdev@vger.kernel.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