From: syzbot <syzbot+9dfc3f3348729cc82277@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, roman.gushchin@linux.dev, shakeelb@google.com,
shaozhengchao@huawei.com, syzkaller-bugs@googlegroups.com,
vasily.averin@linux.dev
Subject: [syzbot] WARNING in default_device_exit_batch (4)
Date: Fri, 18 Nov 2022 03:50:47 -0800 [thread overview]
Message-ID: <000000000000057d3e05edbd51b9@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 81ac25651a62 Merge tag 'nfsd-6.1-5' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16b08501880000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f4e5e9899396248
dashboard link: https://syzkaller.appspot.com/bug?extid=9dfc3f3348729cc82277
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9604c2253fa1/disk-81ac2565.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e1af57bc5afd/vmlinux-81ac2565.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20049443b718/bzImage-81ac2565.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9dfc3f3348729cc82277@syzkaller.appspotmail.com
bond3 (unregistering): Released all slaves
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4036 at net/core/dev.c:10870 unregister_netdevice_many+0x1412/0x1930 net/core/dev.c:10870
Modules linked in:
CPU: 0 PID: 4036 Comm: kworker/u4:8 Not tainted 6.1.0-rc5-syzkaller-00103-g81ac25651a62 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: netns cleanup_net
RIP: 0010:unregister_netdevice_many+0x1412/0x1930 net/core/dev.c:10870
Code: c2 1a 00 00 48 c7 c6 80 60 5b 8b 48 c7 c7 80 61 5b 8b c6 05 8e 50 86 06 01 e8 d7 2f f3 01 0f 0b e9 7a f9 ff ff e8 de 53 c8 f9 <0f> 0b e9 51 f9 ff ff e8 42 17 15 fa e9 b9 ed ff ff 4c 89 ef e8 95
RSP: 0018:ffffc90005cd7a58 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 00000000738d3001 RCX: 0000000000000000
RDX: ffff8880267cd7c0 RSI: ffffffff87b7c5a2 RDI: 0000000000000001
RBP: ffff888060fb1600 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: ffff888060fb1600 R14: ffff88807ad9c000 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ca93a63950 CR3: 000000007f17c000 CR4: 0000000000350ef0
Call Trace:
<TASK>
default_device_exit_batch+0x44d/0x590 net/core/dev.c:11341
ops_exit_list+0x125/0x170 net/core/net_namespace.c:174
cleanup_net+0x4ee/0xb00 net/core/net_namespace.c:601
process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
worker_thread+0x669/0x1090 kernel/workqueue.c:2436
kthread+0x2e8/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
---
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.
next reply other threads:[~2022-11-18 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:50 syzbot [this message]
2023-03-02 10:16 ` [syzbot] [net?] WARNING in default_device_exit_batch (4) 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=000000000000057d3e05edbd51b9@google.com \
--to=syzbot+9dfc3f3348729cc82277@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=shaozhengchao@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vasily.averin@linux.dev \
/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).