From: syzbot <syzbot+df400f2f24a1677cd7e0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: unregister_netdevice: waiting for DEV to become free (4)
Date: Wed, 19 Aug 2020 06:54:23 -0700 [thread overview]
Message-ID: <000000000000568fc005ad3b57c3@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 18445bf4 Merge tag 'spi-fix-v5.9-rc1' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1710d97a900000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb68b9e8a8cc842f
dashboard link: https://syzkaller.appspot.com/bug?extid=df400f2f24a1677cd7e0
compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15859986900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1228fea1900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+df400f2f24a1677cd7e0@syzkaller.appspotmail.com
unregister_netdevice: waiting for lo to become free. Usage count = 1
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-08-19 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 13:54 syzbot [this message]
2020-08-19 14:03 ` unregister_netdevice: waiting for DEV to become free (4) Dmitry Vyukov
2020-08-20 17:07 ` Andrii Nakryiko
2020-08-20 17:15 ` Dmitry Vyukov
2020-08-19 14:51 ` 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=000000000000568fc005ad3b57c3@google.com \
--to=syzbot+df400f2f24a1677cd7e0@syzkaller.appspotmail.com \
--cc=linux-kernel@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