From: syzbot <syzbot+b63f85efcdedbba8b3be@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de, davem@davemloft.net,
hpa@zytor.com, jhs@mojatatu.com, jiri@resnulli.us,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@elte.hu,
mingo@redhat.com, netdev@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vinicius.gomes@intel.com, x86@kernel.org,
xiyou.wangcong@gmail.com
Subject: Re: BUG: soft lockup in __do_sys_clock_adjtime
Date: Sun, 19 Jul 2020 16:02:04 -0700 [thread overview]
Message-ID: <000000000000ec958305aad360e3@google.com> (raw)
In-Reply-To: <0000000000001e16e605a9d01ab3@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=13cb847f100000
start commit: 7cc2a8ea Merge tag 'block-5.8-2020-07-01' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=102b847f100000
console output: https://syzkaller.appspot.com/x/log.txt?x=17cb847f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be693511b29b338
dashboard link: https://syzkaller.appspot.com/bug?extid=b63f85efcdedbba8b3be
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f6948f100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=138eb7a7100000
Reported-by: syzbot+b63f85efcdedbba8b3be@syzkaller.appspotmail.com
Fixes: 5a781ccbd19e ("tc: Add support for configuring the taprio scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2020-07-19 23:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0000000000001e16e605a9d01ab3@google.com>]
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=000000000000ec958305aad360e3@google.com \
--to=syzbot+b63f85efcdedbba8b3be@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vinicius.gomes@intel.com \
--cc=x86@kernel.org \
--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 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).