From: Cong Wang <xiyou.wangcong@gmail.com>
To: Victor Nogueira <victor@mojatatu.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, jhs@mojatatu.com, jiri@resnulli.us,
netdev@vger.kernel.org, pctammela@mojatatu.com,
syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com,
syzbot+5eccb463fa89309d8bdc@syzkaller.appspotmail.com,
syzbot+1261670bbdefc5485a06@syzkaller.appspotmail.com,
syzbot+4dadc5aecf80324d5a51@syzkaller.appspotmail.com,
syzbot+15b96fc3aac35468fe77@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net/sched: Abort __tc_modify_qdisc if parent class does not exist
Date: Fri, 4 Jul 2025 16:54:19 -0700 [thread overview]
Message-ID: <aGhpq58BI8mFpCEs@pop-os.localdomain> (raw)
In-Reply-To: <20250704163422.160424-1-victor@mojatatu.com>
On Fri, Jul 04, 2025 at 01:34:22PM -0300, Victor Nogueira wrote:
> Lion's patch [1] revealed an ancient bug in the qdisc API.
> Whenever a user creates/modifies a qdisc specifying as a parent another
> qdisc, the qdisc API will, during grafting, detect that the user is
> not trying to attach to a class and reject. However grafting is
> performed after qdisc_create (and thus the qdiscs' init callback) is
> executed. In qdiscs that eventually call qdisc_tree_reduce_backlog
> during init or change (such as fq, hhf, choke, etc), an issue
> arises. For example, executing the following commands:
>
> sudo tc qdisc add dev lo root handle a: htb default 2
> sudo tc qdisc add dev lo parent a: handle beef fq
>
> Qdiscs such as fq, hhf, choke, etc unconditionally invoke
> qdisc_tree_reduce_backlog() in their control path init() or change() which
> then causes a failure to find the child class; however, that does not stop
> the unconditional invocation of the assumed child qdisc's qlen_notify with
> a null class. All these qdiscs make the assumption that class is non-null.
>
> The solution is ensure that qdisc_leaf() which looks up the parent
> class, and is invoked prior to qdisc_create(), should return failure on
> not finding the class.
> In this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the
> parentid doesn't correspond to a class, so that we can detect it
> earlier on and abort before qdisc_create is called.
>
Thanks for your quick and excellent catch!
Reviewed-by: Cong Wang <xiyou.wangcong@gmail.com>
Just one additional question, do we still need to safe-guard
qdisc_tree_reduce_backlog()? Below is actually what pops on my mind
immediately after reading your above description (before reading your
code):
diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
index c5e3673aadbe..5a32af623aa4 100644
--- a/net/sched/sch_api.c
+++ b/net/sched/sch_api.c
@@ -817,6 +817,8 @@ void qdisc_tree_reduce_backlog(struct Qdisc *sch, int n, int len)
cops = sch->ops->cl_ops;
if (notify && cops->qlen_notify) {
cl = cops->find(sch, parentid);
+ if (!cl)
+ break;
cops->qlen_notify(sch, cl);
}
sch->q.qlen -= n;
next prev parent reply other threads:[~2025-07-04 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 16:34 [PATCH net] net/sched: Abort __tc_modify_qdisc if parent class does not exist Victor Nogueira
2025-07-04 23:54 ` Cong Wang [this message]
2025-07-05 14:03 ` Jamal Hadi Salim
2025-07-07 13:59 ` Jakub Kicinski
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=aGhpq58BI8mFpCEs@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=syzbot+1261670bbdefc5485a06@syzkaller.appspotmail.com \
--cc=syzbot+15b96fc3aac35468fe77@syzkaller.appspotmail.com \
--cc=syzbot+4dadc5aecf80324d5a51@syzkaller.appspotmail.com \
--cc=syzbot+5eccb463fa89309d8bdc@syzkaller.appspotmail.com \
--cc=syzbot+d8b58d7b0ad89a678a16@syzkaller.appspotmail.com \
--cc=victor@mojatatu.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;
as well as URLs for NNTP newsgroup(s).