From: syzbot <syzbot+6174a6c5eba4b3cdd606@syzkaller.appspotmail.com>
To: davem@davemloft.net, jon.maloy@ericsson.com,
keescook@chromium.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, luto@amacapital.net,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, wad@chromium.org,
ying.xue@windriver.com, yoshfuji@linux-ipv6.org
Subject: Re: WARNING: locking bug in __queue_work
Date: Sat, 16 Mar 2019 07:49:01 -0700 [thread overview]
Message-ID: <00000000000095d9b205843741bd@google.com> (raw)
In-Reply-To: <0000000000000655c0057cd141f1@google.com>
syzbot has bisected this bug to:
commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
Author: Jon Maloy <jon.maloy@ericsson.com>
Date: Thu Mar 22 19:42:52 2018 +0000
tipc: obtain node identity from interface by default
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152adcd7200000
start commit: 52dfae5c tipc: obtain node identity from interface by defa..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=172adcd7200000
console output: https://syzkaller.appspot.com/x/log.txt?x=132adcd7200000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
dashboard link: https://syzkaller.appspot.com/bug?extid=6174a6c5eba4b3cdd606
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11635d24c00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f2ed58c00000
Reported-by: syzbot+6174a6c5eba4b3cdd606@syzkaller.appspotmail.com
Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")
next prev parent reply other threads:[~2019-03-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:11 WARNING: locking bug in __queue_work syzbot
2019-02-15 16:37 ` syzbot
2019-03-16 14:49 ` syzbot [this message]
2020-06-17 18:34 ` 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=00000000000095d9b205843741bd@google.com \
--to=syzbot+6174a6c5eba4b3cdd606@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=keescook@chromium.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=wad@chromium.org \
--cc=ying.xue@windriver.com \
--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 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).