From: syzbot <syzbot+a50c7541a4a55cd49b02@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, davem@davemloft.net,
jiangshanlai@gmail.com, kuznet@ms2.inr.ac.ru,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sbrivio@redhat.com, sd@queasysnail.net,
syzkaller-bugs@googlegroups.com, tj@kernel.org, tytso@mit.edu,
viro@zeniv.linux.org.uk, yoshfuji@linux-ipv6.org
Subject: Re: possible deadlock in flush_workqueue (2)
Date: Fri, 22 Mar 2019 04:12:00 -0700 [thread overview]
Message-ID: <0000000000007ccc900584acecc1@google.com> (raw)
In-Reply-To: <000000000000bfd4270578abe88b@google.com>
syzbot has bisected this bug to:
commit f547fac624be53ad8b07e9ebca7654a7827ba61b
Author: Sabrina Dubroca <sd@queasysnail.net>
Date: Fri Oct 12 14:22:47 2018 +0000
ipv6: rate-limit probes for neighbourless routes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17affd1b200000
start commit: f547fac6 ipv6: rate-limit probes for neighbourless routes
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=146ffd1b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=106ffd1b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=963b24abf3f7c2d8
dashboard link: https://syzkaller.appspot.com/bug?extid=a50c7541a4a55cd49b02
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12097f03400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b55ac5400000
Reported-by: syzbot+a50c7541a4a55cd49b02@syzkaller.appspotmail.com
Fixes: f547fac624be ("ipv6: rate-limit probes for neighbourless routes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-22 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 16:57 possible deadlock in flush_workqueue (2) syzbot
2018-10-23 9:42 ` syzbot
2018-10-23 14:28 ` Theodore Y. Ts'o
2018-10-23 19:40 ` Tejun Heo
2019-03-22 11:12 ` syzbot [this message]
2019-11-07 13:42 ` syzbot
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=0000000000007ccc900584acecc1@google.com \
--to=syzbot+a50c7541a4a55cd49b02@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=davem@davemloft.net \
--cc=jiangshanlai@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yoshfuji@linux-ipv6.org \
/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.