From: syzbot <syzbot+de9526ade17c659d8336@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] INFO: rcu detected stall in __hrtimer_run_queues
Date: Sun, 27 Mar 2022 03:59:16 -0700 [thread overview]
Message-ID: <00000000000035bee505db3116b7@google.com> (raw)
In-Reply-To: <20220327092631.4171-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+de9526ade17c659d8336@syzkaller.appspotmail.com
Tested on:
commit: f0228146 Merge tag 'trace-v5.18-1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=abe260d3ec31020f
dashboard link: https://syzkaller.appspot.com/bug?extid=de9526ade17c659d8336
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-03-27 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220327092631.4171-1-hdanton@sina.com>
2022-03-27 10:59 ` syzbot [this message]
[not found] <20220731110143.913-1-hdanton@sina.com>
2022-07-31 11:13 ` [syzbot] INFO: rcu detected stall in __hrtimer_run_queues syzbot
[not found] <20220731093631.791-1-hdanton@sina.com>
2022-07-31 9:53 ` syzbot
[not found] <20220731082711.724-1-hdanton@sina.com>
2022-07-31 8:47 ` syzbot
[not found] <20220731080330.602-1-hdanton@sina.com>
2022-07-31 8:19 ` syzbot
[not found] <20220731072530.451-1-hdanton@sina.com>
2022-07-31 7:38 ` syzbot
2021-02-20 21:05 syzbot
2021-11-16 15:41 ` [syzbot] " syzbot
2021-11-16 15:42 ` Jens Axboe
2021-11-17 11:59 ` Paul E. McKenney
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=00000000000035bee505db3116b7@google.com \
--to=syzbot+de9526ade17c659d8336@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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).