From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+2642f347f7309b4880dc@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in exit_to_user_mode_loop
Date: Tue, 29 Jul 2025 09:06:56 +0800 [thread overview]
Message-ID: <20250729010657.3326-1-hdanton@sina.com> (raw)
In-Reply-To: <6887ebf4.a00a0220.b12ec.00ae.GAE@google.com>
> Date: Mon, 28 Jul 2025 14:30:28 -0700 [thread overview]
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: afd8c2c9e2e2 Merge branch 'ipv6-f6i-fib6_siblings-and-rt-f..
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=13c71034580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a4bcc0a11b3192be
> dashboard link: https://syzkaller.appspot.com/bug?extid=2642f347f7309b4880dc
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17b284a2580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17c71034580000
#syz test upstream master
--- x/net/sched/sch_taprio.c
+++ y/net/sched/sch_taprio.c
@@ -918,7 +918,7 @@ static enum hrtimer_restart advance_sche
int num_tc = netdev_get_num_tc(dev);
struct sched_entry *entry, *next;
struct Qdisc *sch = q->root;
- ktime_t end_time;
+ ktime_t end_time, now;
int tc;
spin_lock(&q->current_entry_lock);
@@ -980,6 +980,11 @@ first_run:
rcu_assign_pointer(q->current_entry, next);
spin_unlock(&q->current_entry_lock);
+ now = timer->base->get_time();
+ now = ktime_add_us(now, 2);
+ /* is end_time sane? */
+ if (ktime_after(now, end_time))
+ end_time = now;
hrtimer_set_expires(&q->advance_timer, end_time);
rcu_read_lock();
--
next prev parent reply other threads:[~2025-07-29 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 15:44 syzbot
2025-07-12 0:18 ` syzbot
2025-07-28 21:30 ` syzbot
2025-07-29 1:06 ` Hillf Danton [this message]
2025-07-29 4:47 ` syzbot
2026-08-17 7:21 ` Junjie Cao
2026-08-17 6:02 ` syzbot
2026-08-31 8:41 ` Junjie Cao
2026-08-31 11:12 ` syzbot
2026-09-01 1:43 ` Junjie Cao
2026-09-01 8:22 ` 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=20250729010657.3326-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2642f347f7309b4880dc@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®