From: syzbot <syzbot+1261670bbdefc5485a06@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [net?] general protection fault in qdisc_tree_reduce_backlog
Date: Thu, 03 Jul 2025 23:36:48 -0700 [thread overview]
Message-ID: <68677680.a00a0220.c7b3.0016.GAE@google.com> (raw)
In-Reply-To: <686764a5.a00a0220.c7b3.0013.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [net?] general protection fault in qdisc_tree_reduce_backlog
Author: lizhi.xu@windriver.com
#syz test
diff --git a/net/sched/sch_api.c b/net/sched/sch_api.c
index d8a33486c51..7f32347971f 100644
--- a/net/sched/sch_api.c
+++ b/net/sched/sch_api.c
@@ -803,12 +803,13 @@ void qdisc_tree_reduce_backlog(struct Qdisc *sch, int n, int len)
break;
}
cops = sch->ops->cl_ops;
- if (notify && cops->qlen_notify) {
+ if (cops && notify && cops->qlen_notify) {
/* Note that qlen_notify must be idempotent as it may get called
* multiple times.
*/
cl = cops->find(sch, parentid);
- cops->qlen_notify(sch, cl);
+ if (virt_addr_valid(cl))
+ cops->qlen_notify(sch, cl);
}
sch->q.qlen -= n;
sch->qstats.backlog -= len;
next prev parent reply other threads:[~2025-07-04 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 5:20 [syzbot] [net?] general protection fault in qdisc_tree_reduce_backlog syzbot
2025-07-04 6:36 ` syzbot [this message]
2025-07-04 7:25 ` Hillf Danton
2025-07-04 7:53 ` syzbot
2025-07-04 8:04 ` [PATCH] net/sched: Prevent notify to parent who unsupport class ops Lizhi Xu
2025-07-04 14:01 ` Paolo Abeni
2025-07-05 0:03 ` Cong Wang
2025-07-05 1:18 ` [PATCH V2] " Lizhi Xu
2025-07-05 5:07 ` Cong Wang
2025-07-05 13:59 ` Jamal Hadi Salim
2025-07-04 8:34 ` [syzbot] [net?] general protection fault in qdisc_tree_reduce_backlog syzbot
2025-07-05 8:42 ` Hillf Danton
2025-07-05 9:12 ` syzbot
[not found] <20250704063547.3973319-1-lizhi.xu@windriver.com>
2025-07-04 7:30 ` syzbot
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=68677680.a00a0220.c7b3.0016.GAE@google.com \
--to=syzbot+1261670bbdefc5485a06@syzkaller.appspotmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.