From: syzbot <syzbot+40918e4d826fb2ff9b96@syzkaller.appspotmail.com>
To: avagin@virtuozzo.com, davem@davemloft.net, ebiederm@xmission.com,
edumazet@google.com, ktkhai@virtuozzo.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tyhicks@canonical.com,
willy@infradead.org
Subject: WARNING in rollback_registered_many (2)
Date: Wed, 07 Nov 2018 11:00:04 -0800 [thread overview]
Message-ID: <000000000000d9f094057a17b97b@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 042cb5647815 net: phy: Allow BCM54616S PHY to setup intern..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=15c0102b400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f559fee2fc3375a
dashboard link: https://syzkaller.appspot.com/bug?extid=40918e4d826fb2ff9b96
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+40918e4d826fb2ff9b96@syzkaller.appspotmail.com
device bridge_slave_0 left promiscuous mode
��: port 1(bridge_slave_0) entered disabled state
bond2 (unregistering): Released all slaves
bond1 (unregistering): Released all slaves
bond0 (unregistering): Released all slaves
WARNING: CPU: 1 PID: 9748 at net/core/dev.c:8022
rollback_registered_many+0xeca/0x1250 net/core/dev.c:8022
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 9748 Comm: kworker/u4:5 Not tainted 4.20.0-rc1+ #174
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Workqueue: netns cleanup_net
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x244/0x39d lib/dump_stack.c:113
panic+0x2ad/0x55c kernel/panic.c:188
__warn.cold.8+0x20/0x45 kernel/panic.c:540
report_bug+0x254/0x2d0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
do_error_trap+0x11b/0x200 arch/x86/kernel/traps.c:271
do_invalid_op+0x36/0x40 arch/x86/kernel/traps.c:290
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:969
RIP: 0010:rollback_registered_many+0xeca/0x1250 net/core/dev.c:8022
Code: 57 19 00 00 48 c7 c6 e0 01 bb 88 48 c7 c7 20 02 bb 88 c6 05 ea 2e ed
03 01 e8 e2 c0 24 fb 0f 0b e9 a6 f9 ff ff e8 06 5f 5b fb <0f> 0b e9 7b f9
ff ff e8 fa 5e 5b fb 0f 0b e9 ea f9 ff ff e8 ee 5e
RSP: 0018:ffff8801bbc17058 EFLAGS: 00010293
RAX: ffff880187848280 RBX: ffff880192c31240 RCX: ffffffff86242533
RDX: 0000000000000000 RSI: ffffffff86242bba RDI: 0000000000000001
RBP: ffff8801bbc172a0 R08: ffff880187848280 R09: fffffbfff13dee60
R10: fffffbfff13dee60 R11: ffffffff89ef7307 R12: dffffc0000000000
R13: 0000000000000001 R14: ffffffff84889300 R15: ffff8801bbc17138
unregister_netdevice_many+0xfa/0x4c0 net/core/dev.c:9107
default_device_exit_batch+0x43a/0x540 net/core/dev.c:9576
ops_exit_list.isra.5+0x105/0x160 net/core/net_namespace.c:156
cleanup_net+0x555/0xb10 net/core/net_namespace.c:551
process_one_work+0xc90/0x1c40 kernel/workqueue.c:2153
worker_thread+0x17f/0x1390 kernel/workqueue.c:2296
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
next reply other threads:[~2018-11-07 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 19:00 syzbot [this message]
2019-04-11 23:29 ` WARNING in rollback_registered_many (2) syzbot
2019-04-12 11:32 ` Andrey Konovalov
2019-08-07 14:03 ` Andrey Konovalov
2019-08-22 13:07 ` Andrey Konovalov
2019-08-22 14:54 ` Andrey Konovalov
2019-08-22 14:06 ` Oliver Neukum
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=000000000000d9f094057a17b97b@google.com \
--to=syzbot+40918e4d826fb2ff9b96@syzkaller.appspotmail.com \
--cc=avagin@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tyhicks@canonical.com \
--cc=willy@infradead.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.