From: syzbot <syzbot+ba21d65f55b562432c58@syzkaller.appspotmail.com>
To: davem@davemloft.net, jon.maloy@ericsson.com,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com,
yoshfuji@linux-ipv6.org
Subject: Re: WARNING: locking bug in icmp_send
Date: Sat, 23 Mar 2019 11:03:01 -0700 [thread overview]
Message-ID: <0000000000003d44980584c6c82a@google.com> (raw)
In-Reply-To: <000000000000bc227a0582464e62@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=11b6dc5d200000
start commit: b5372fe5 exec: load_script: Do not exec truncated interpre..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=13b6dc5d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=15b6dc5d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f
dashboard link: https://syzkaller.appspot.com/bug?extid=ba21d65f55b562432c58
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c90fa7400000
Reported-by: syzbot+ba21d65f55b562432c58@syzkaller.appspotmail.com
Fixes: 52dfae5c85a4 ("tipc: obtain node identity from interface by default")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-23 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:56 WARNING: locking bug in icmp_send syzbot
2019-03-23 18:03 ` syzbot [this message]
2019-03-25 16:34 ` Jon Maloy
2019-05-09 13:01 ` Dmitry Vyukov
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=0000000000003d44980584c6c82a@google.com \
--to=syzbot+ba21d65f55b562432c58@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--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 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.