Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
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

      reply	other threads:[~2020-07-25  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 18:22 syzbot
2020-07-25  5:11 ` 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=000000000000c641a505ab3d1d48@google.com \
    --to=syzbot+0c6da80218456f1edc36@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=linux-fsdevel@vger.kernel.org \
    --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=viro@zeniv.linux.org.uk \
    --cc=xiyou.wangcong@gmail.com \
    --subject='Re: INFO: task hung in synchronize_rcu (3)' \
    /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

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).