From: syzbot <syzbot+2dfb68e639f0621b19fb@syzkaller.appspotmail.com>
To: ddstreet@ieee.org, dvyukov@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: unregister_netdevice: waiting for DEV to become free
Date: Fri, 20 Apr 2018 16:59:02 -0700 [thread overview]
Message-ID: <000000000000ed9844056a507832@google.com> (raw)
In-Reply-To: <000000000000d71bf6056a34b628@google.com>
syzbot has found reproducer for the following crash on
https://github.com/google/kmsan.git/master commit
48c6a2b0ab1b752451cdc40b5392471ed1a2a329 (Mon Apr 16 08:42:26 2018 +0000)
mm/kmsan: fix origin calculation in kmsan_internal_check_memory
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=2dfb68e639f0621b19fb
So far this crash happened 180 times on
https://github.com/google/kmsan.git/master, net-next, upstream.
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=4936564132020224
syzkaller reproducer:
https://syzkaller.appspot.com/x/repro.syz?id=5817131010621440
Raw console output:
https://syzkaller.appspot.com/x/log.txt?id=6313498770407424
Kernel config:
https://syzkaller.appspot.com/x/.config?id=6627248707860932248
compiler: clang version 7.0.0 (trunk 329391)
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+2dfb68e639f0621b19fb@syzkaller.appspotmail.com
It will help syzbot understand when the bug is fixed.
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
device bridge_slave_1 left promiscuous mode
bridge0: port 2(bridge_slave_1) entered disabled state
device bridge_slave_0 left promiscuous mode
bridge0: port 1(bridge_slave_0) entered disabled state
unregister_netdevice: waiting for lo to become free. Usage count = 3
next prev parent reply other threads:[~2018-04-20 23:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 14:52 unregister_netdevice: waiting for DEV to become free syzbot
2018-04-19 14:53 ` Dmitry Vyukov
2018-04-20 23:59 ` syzbot [this message]
2018-07-27 13:00 ` Tetsuo Handa
2018-07-31 11:16 ` Tetsuo Handa
2018-07-31 11:31 ` Steffen Klassert
2018-08-01 8:57 ` Steffen Klassert
2018-08-01 9:14 ` 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=000000000000ed9844056a507832@google.com \
--to=syzbot+2dfb68e639f0621b19fb@syzkaller.appspotmail.com \
--cc=ddstreet@ieee.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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