[v6.1] WARNING in default_device_exit_batch (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 420102835862 Linux 6.1.134
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f49a6f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b6a16d457784cab
dashboard link: https://syzkaller.appspot.com/bug?extid=3088d9457fa2edad768f
compiler: Debian clang version 15.0.6, Debian LLD 15.0.6
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ebd558063376/disk-42010283.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8fddad580749/vmlinux-42010283.xz
kernel image: https://storage.googleapis.com/syzbot-assets/557917aaa3df/Image-42010283.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3088d9...@syzkaller.appspotmail.com

device hsr_slave_0 left promiscuous mode
device hsr_slave_1 left promiscuous mode
------------[ cut here ]------------
WARNING: CPU: 0 PID: 177 at net/core/dev.c:9227 dev_xdp_install net/core/dev.c:9207 [inline]
WARNING: CPU: 0 PID: 177 at net/core/dev.c:9227 dev_xdp_uninstall net/core/dev.c:9227 [inline]
WARNING: CPU: 0 PID: 177 at net/core/dev.c:9227 unregister_netdevice_many+0xb84/0x1798 net/core/dev.c:10971
Modules linked in:
CPU: 0 PID: 177 Comm: kworker/u4:3 Not tainted 6.1.134-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: netns cleanup_net
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : dev_xdp_uninstall net/core/dev.c:9207 [inline]
pc : unregister_netdevice_many+0xb84/0x1798 net/core/dev.c:10971
lr : dev_xdp_install net/core/dev.c:9207 [inline]
lr : dev_xdp_uninstall net/core/dev.c:9227 [inline]
lr : unregister_netdevice_many+0xb84/0x1798 net/core/dev.c:10971
sp : ffff800021297740
x29: ffff800021297880 x28: ffff8000212979a0 x27: ffff0000c4bb4060
x26: ffff0000c4bb4c00 x25: ffff0000c4bb40d0 x24: ffff800021002000
x23: ffff0000c4bb4c08 x22: ffff800021297800 x21: 1fffe00018976981
x20: 00000000ffffffa1 x19: dfff800000000000 x18: 1fffe00036798976
x17: ffff8000106293fc x16: ffff8000084f3ce0 x15: 0000000000000000
x14: 0000000000000004 x13: ffff0000c93c1bc0 x12: 0000000000ff0100
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80001061907c
x8 : ffff0000c93c1bc0 x7 : 0000000000000000 x6 : ffff800008971a74
x5 : ffff0000f4961480 x4 : 0000000000000000 x3 : ffff8000082f7ce8
x2 : 0000000000000000 x1 : 00000000ffffffa1 x0 : 0000000000000000
Call trace:
dev_xdp_install net/core/dev.c:9207 [inline]
dev_xdp_uninstall net/core/dev.c:9227 [inline]
unregister_netdevice_many+0xb84/0x1798 net/core/dev.c:10971
default_device_exit_batch+0xa10/0xaa8 net/core/dev.c:11491
ops_exit_list net/core/net_namespace.c:177 [inline]
cleanup_net+0x6b8/0xaec net/core/net_namespace.c:640
process_one_work+0x804/0x1484 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
irq event stamp: 1347328
hardirqs last enabled at (1347327): [<ffff800008392b0c>] call_rcu+0x614/0xa40 kernel/rcu/tree.c:2880
hardirqs last disabled at (1347328): [<ffff80001231a92c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (1347238): [<ffff8000081c40ac>] softirq_handle_end kernel/softirq.c:421 [inline]
softirqs last enabled at (1347238): [<ffff8000081c40ac>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:606
softirqs last disabled at (1347229): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:612
---[ end trace 0000000000000000 ]---
bond1 (unregistering): Released all slaves
bond0 (unregistering): Released all slaves
IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.