From: syzbot <syzbot+0c6da80218456f1edc36@syzkaller•appspotmail.com>
To: akpm@linux-foundation•org, davem@davemloft•net, jhs@mojatatu•com,
jiri@resnulli•us, linux-fsdevel@vger•kernel.org,
linux-kernel@vger•kernel.org, mingo@elte•hu,
netdev@vger•kernel.org, peterz@infradead•org,
syzkaller-bugs@googlegroups•com, tglx@linutronix•de,
vinicius.gomes@intel•com, viro@zeniv•linux.org.uk,
xiyou.wangcong@gmail•com
Subject: Re: INFO: task hung in synchronize_rcu (3)
Date: Fri, 24 Jul 2020 22:11:04 -0700 [thread overview]
Message-ID: <000000000000c641a505ab3d1d48@google.com> (raw)
In-Reply-To: <000000000000402c5305ab0bd2a2@google.com>
syzbot has bisected this issue to:
commit 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22
Author: Vinicius Costa Gomes <vinicius.gomes@intel•com>
Date: Sat Sep 29 00:59:43 2018 +0000
tc: Add support for configuring the taprio scheduler
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=149057ef100000
start commit: 4fa640dc Merge tag 'vfio-v5.8-rc7' of git://github.com/awi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=169057ef100000
console output: https://syzkaller.appspot.com/x/log.txt?x=129057ef100000
kernel config: https://syzkaller.appspot.com/x/.config?x=f87a5e4232fdb267
dashboard link: https://syzkaller.appspot.com/bug?extid=0c6da80218456f1edc36
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e2a437100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13af00e8900000
Reported-by: syzbot+0c6da80218456f1edc36@syzkaller•appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2020-07-25 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000402c5305ab0bd2a2@google.com>
2020-07-25 5:11 ` syzbot [this message]
2022-05-10 8:51 ` [syzbot] INFO: task hung in synchronize_rcu (3) syzbot
2022-05-10 13:45 ` Sean Christopherson
2022-05-10 13:50 ` Paolo Bonzini
2022-05-10 13:56 ` Sean Christopherson
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=000000000000c641a505ab3d1d48@google.com \
--to=syzbot+0c6da80218456f1edc36@syzkaller$(echo .)appspotmail.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peterz@infradead$(echo .)org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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