From: syzbot <syzbot+f3bd350a4124f10acdae@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net, jhs@mojatatu.com,
jiri@resnulli.us, 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, xiyou.wangcong@gmail.com
Subject: Re: INFO: rcu detected stall in sys_clock_settime
Date: Sun, 19 Jul 2020 10:16:07 -0700 [thread overview]
Message-ID: <000000000000b0fb8b05aace8b8e@google.com> (raw)
In-Reply-To: <000000000000418fc105aa4243aa@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=167142f0900000
start commit: e9919e11 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=157142f0900000
console output: https://syzkaller.appspot.com/x/log.txt?x=117142f0900000
kernel config: https://syzkaller.appspot.com/x/.config?x=a160d1053fc89af5
dashboard link: https://syzkaller.appspot.com/bug?extid=f3bd350a4124f10acdae
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1353c420900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130f8ef7100000
Reported-by: syzbot+f3bd350a4124f10acdae@syzkaller.appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-07-19 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 17:54 INFO: rcu detected stall in sys_clock_settime syzbot
2020-07-19 17:16 ` syzbot [this message]
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=000000000000b0fb8b05aace8b8e@google.com \
--to=syzbot+f3bd350a4124f10acdae@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@gmail.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 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.