* [moderation/CI] Re: net: opt loopback into instance locking
@ 2026-09-21 3:11 syzbot ci
2026-09-21 3:21 ` Aleksandr Nogikh
0 siblings, 1 reply; 4+ messages in thread
From: syzbot ci @ 2026-09-21 3:11 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v1] net: opt loopback into instance locking
https://lore.kernel.org/all/20260918210419.4088201-1-kuba@kernel.org
* [PATCH net-next] net: opt loopback into instance locking
and found the following issue:
WARNING in ipv6_add_dev
Full report is available here:
https://ci.syzbot.org/series/f12bc892-cfa6-4277-beac-794482c9a3f7
***
WARNING in ipv6_add_dev
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 8830e65ed46de41f849eefb8ba227d4852c460f6
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/ae142b5c-beb2-4c41-814c-2cd3e14bdbb0/config
usbcore: registered new interface driver snd-usb-hiface
usbcore: registered new interface driver snd-bcd2000
usbcore: registered new interface driver snd_usb_pod
usbcore: registered new interface driver snd_usb_podhd
usbcore: registered new interface driver snd_usb_toneport
usbcore: registered new interface driver snd_usb_variax
drop_monitor: Initializing network drop monitor service
NET: Registered PF_LLC protocol family
GACT probability on
Mirror/redirect action on
Simple TC action Loaded
u32 classifier
Performance counters on
input device check on
Actions configured
nf_conntrack_irc: The irc conntrack helper is scheduled for removal.
Please contact the netfilter-devel mailing list if you still need this.
The pptp conntrack helper is scheduled for removal.
Please contact the netfilter-devel mailing list if you still need this.
The DCCP match is deprecated and scheduled to be removed in 2027.
Please contact the netfilter-devel mailing list or update your iptables rules
xt_time: kernel timezone is -0000
IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
IPVS: ipvs loaded.
IPVS: [rr] scheduler registered.
IPVS: [wrr] scheduler registered.
IPVS: [lc] scheduler registered.
IPVS: [wlc] scheduler registered.
IPVS: [fo] scheduler registered.
IPVS: [ovf] scheduler registered.
IPVS: [lblc] scheduler registered.
IPVS: [lblcr] scheduler registered.
IPVS: [dh] scheduler registered.
IPVS: [sh] scheduler registered.
IPVS: [mh] scheduler registered.
IPVS: [sed] scheduler registered.
IPVS: [nq] scheduler registered.
IPVS: [twos] scheduler registered.
IPVS: [sip] pe registered.
ipip: IPv4 and MPLS over IPv4 tunneling driver
gre: GRE over IPv4 demultiplexer driver
ip_gre: GRE over IPv4 tunneling driver
IPv4 over IPsec tunneling driver
Initializing XFRM netlink socket
IPsec XFRM device driver
xfrm_iptfs: IPsec IP-TFS tunnel mode module
NET: Registered PF_INET6 protocol family
------------[ cut here ]------------
debug_locks && !(lock_is_held(&(&dev->lock)->dep_map) != 0)
WARNING: ./include/net/netdev_lock.h:70 at ipv6_add_dev+0xfc1/0x1400, CPU#0: swapper/0/1
Modules linked in:
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:ipv6_add_dev+0xfc1/0x1400
Code: ff ff e8 a2 6e 3a f7 48 8d 3d 6b 56 fd 05 48 c7 c6 80 a2 32 8d ba 80 01 00 00 67 48 0f b9 3a e9 ab f0 ff ff e8 80 6e 3a f7 90 <0f> 0b 90 e9 cb f1 ff ff e8 72 6e 3a f7 48 8d 3d 5b 56 fd 05 48 c7
RSP: 0000:ffffc900000678c0 EFLAGS: 00010293
RAX: ffffffff8a8d6400 RBX: dffffc0000000000 RCX: ffff888102abda00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff90253707 R09: 1ffffffff204a6e0
R10: dffffc0000000000 R11: fffffbfff204a6e1 R12: dffffc0000000000
R13: ffff88810c036000 R14: ffffffff8caa6a10 R15: ffff88810c036008
FS: 0000000000000000(0000) GS:ffff88818d6cd000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000eb48000 CR4: 00000000000006f0
Call Trace:
<TASK>
addrconf_init+0x8b/0x170
inet6_init+0x228/0x3f0
do_one_initcall+0x250/0x870
do_initcall_level+0x10a/0x1a0
do_initcalls+0x59/0xa0
kernel_init_freeable+0x29d/0x3e0
kernel_init+0x22/0x1d0
ret_from_fork+0x514/0xb70
ret_from_fork_asm+0x1a/0x30
</TASK>
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com horms@kernel.org kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [moderation/CI] Re: net: opt loopback into instance locking
2026-09-21 3:11 [moderation/CI] Re: net: opt loopback into instance locking syzbot ci
@ 2026-09-21 3:21 ` Aleksandr Nogikh
0 siblings, 0 replies; 4+ messages in thread
From: Aleksandr Nogikh @ 2026-09-21 3:21 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Sun, Sep 20, 2026 at 11:11 PM syzbot ci
<syzbot+ci82cbe6e020993733@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v1] net: opt loopback into instance locking
> https://lore.kernel.org/all/20260918210419.4088201-1-kuba@kernel.org
> * [PATCH net-next] net: opt loopback into instance locking
>
> and found the following issue:
> WARNING in ipv6_add_dev
>
> Full report is available here:
> https://ci.syzbot.org/series/f12bc892-cfa6-4277-beac-794482c9a3f7
>
> ***
>
> WARNING in ipv6_add_dev
>
> tree: net-next
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
> base: 8830e65ed46de41f849eefb8ba227d4852c460f6
> arch: amd64
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> config: https://ci.syzbot.org/builds/ae142b5c-beb2-4c41-814c-2cd3e14bdbb0/config
>
> usbcore: registered new interface driver snd-usb-hiface
> usbcore: registered new interface driver snd-bcd2000
> usbcore: registered new interface driver snd_usb_pod
> usbcore: registered new interface driver snd_usb_podhd
> usbcore: registered new interface driver snd_usb_toneport
> usbcore: registered new interface driver snd_usb_variax
> drop_monitor: Initializing network drop monitor service
> NET: Registered PF_LLC protocol family
> GACT probability on
> Mirror/redirect action on
> Simple TC action Loaded
> u32 classifier
> Performance counters on
> input device check on
> Actions configured
> nf_conntrack_irc: The irc conntrack helper is scheduled for removal.
> Please contact the netfilter-devel mailing list if you still need this.
> The pptp conntrack helper is scheduled for removal.
> Please contact the netfilter-devel mailing list if you still need this.
> The DCCP match is deprecated and scheduled to be removed in 2027.
> Please contact the netfilter-devel mailing list or update your iptables rules
> xt_time: kernel timezone is -0000
> IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
> IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
> IPVS: ipvs loaded.
> IPVS: [rr] scheduler registered.
> IPVS: [wrr] scheduler registered.
> IPVS: [lc] scheduler registered.
> IPVS: [wlc] scheduler registered.
> IPVS: [fo] scheduler registered.
> IPVS: [ovf] scheduler registered.
> IPVS: [lblc] scheduler registered.
> IPVS: [lblcr] scheduler registered.
> IPVS: [dh] scheduler registered.
> IPVS: [sh] scheduler registered.
> IPVS: [mh] scheduler registered.
> IPVS: [sed] scheduler registered.
> IPVS: [nq] scheduler registered.
> IPVS: [twos] scheduler registered.
> IPVS: [sip] pe registered.
> ipip: IPv4 and MPLS over IPv4 tunneling driver
> gre: GRE over IPv4 demultiplexer driver
> ip_gre: GRE over IPv4 tunneling driver
> IPv4 over IPsec tunneling driver
> Initializing XFRM netlink socket
> IPsec XFRM device driver
> xfrm_iptfs: IPsec IP-TFS tunnel mode module
> NET: Registered PF_INET6 protocol family
> ------------[ cut here ]------------
> debug_locks && !(lock_is_held(&(&dev->lock)->dep_map) != 0)
> WARNING: ./include/net/netdev_lock.h:70 at ipv6_add_dev+0xfc1/0x1400, CPU#0: swapper/0/1
> Modules linked in:
> CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:ipv6_add_dev+0xfc1/0x1400
> Code: ff ff e8 a2 6e 3a f7 48 8d 3d 6b 56 fd 05 48 c7 c6 80 a2 32 8d ba 80 01 00 00 67 48 0f b9 3a e9 ab f0 ff ff e8 80 6e 3a f7 90 <0f> 0b 90 e9 cb f1 ff ff e8 72 6e 3a f7 48 8d 3d 5b 56 fd 05 48 c7
> RSP: 0000:ffffc900000678c0 EFLAGS: 00010293
> RAX: ffffffff8a8d6400 RBX: dffffc0000000000 RCX: ffff888102abda00
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 0000000000000000 R08: ffffffff90253707 R09: 1ffffffff204a6e0
> R10: dffffc0000000000 R11: fffffbfff204a6e1 R12: dffffc0000000000
> R13: ffff88810c036000 R14: ffffffff8caa6a10 R15: ffff88810c036008
> FS: 0000000000000000(0000) GS:ffff88818d6cd000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff88823ffff000 CR3: 000000000eb48000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> addrconf_init+0x8b/0x170
> inet6_init+0x228/0x3f0
> do_one_initcall+0x250/0x870
> do_initcall_level+0x10a/0x1a0
> do_initcalls+0x59/0xa0
> kernel_init_freeable+0x29d/0x3e0
> kernel_init+0x22/0x1d0
> ret_from_fork+0x514/0xb70
> ret_from_fork_asm+0x1a/0x30
> </TASK>
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> To test a fix for this bug, please reply with `#syz test`
> (on a separate line) and attach the patch to the email.
>
> Notes:
> - The patch will be applied on top of the tested series (as an
> incremental fix).
> - To test a new version of the whole series, please send it directly
> to syzbot@lists.linux.dev.
> - Arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [andrew@lunn.ch davem@davemloft.net edumazet@google.com horms@kernel.org kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6ab0a06e.514bccd6.255447.000c.GAE%40google.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [moderation/CI] Re: net: opt loopback into instance locking
@ 2026-09-23 23:45 syzbot ci
2026-09-24 2:39 ` Aleksandr Nogikh
0 siblings, 1 reply; 4+ messages in thread
From: syzbot ci @ 2026-09-23 23:45 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v2] net: opt loopback into instance locking
https://lore.kernel.org/all/20260921190452.1467853-1-kuba@kernel.org
* [PATCH net-next v2] net: opt loopback into instance locking
and found the following issue:
possible deadlock in default_device_exit_batch
Full report is available here:
https://ci.syzbot.org/series/23f51d46-5d1a-4839-a0a8-35d88361ffdb
***
possible deadlock in default_device_exit_batch
tree: net-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
base: 944ae66642b726bd6b25ae71b1e9ff88a0e0bdb0
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/014063b0-7001-43f1-aa04-57649607febc/config
AI triage: https://ci.syzbot.org/findings/6bb35d14-7fe7-4d73-9528-891c80cf7f1c/triage_trajectory
batman_adv: batadv0: Removing interface: batadv_slave_0
batman_adv: batadv0: Removing interface: batadv_slave_1
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u8:3/5652 is trying to acquire lock:
ffff88811671ae70 (&dev_instance_lock_key#3){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
but task is already holding lock:
ffff88816d8dae70 (&dev_instance_lock_key){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&dev_instance_lock_key){+.+.}-{4:4}:
__mutex_lock+0x19d/0x1550
unregister_netdevice_many_notify+0x5bb/0x2140
default_device_exit_batch+0x6d4/0x760
ops_undo_list+0x4b4/0x8d0
cleanup_net+0x572/0x810
process_scheduled_works+0xc3d/0x1630
worker_thread+0xa47/0xfb0
kthread+0x38b/0x480
ret_from_fork+0x514/0xb70
ret_from_fork_asm+0x1a/0x30
-> #0 (&dev_instance_lock_key#3){+.+.}-{4:4}:
__lock_acquire+0x164c/0x2de0
lock_acquire+0x115/0x350
__mutex_lock+0x19d/0x1550
unregister_netdevice_many_notify+0x5bb/0x2140
default_device_exit_batch+0x6d4/0x760
ops_undo_list+0x4b4/0x8d0
cleanup_net+0x572/0x810
process_scheduled_works+0xc3d/0x1630
worker_thread+0xa47/0xfb0
kthread+0x38b/0x480
ret_from_fork+0x514/0xb70
ret_from_fork_asm+0x1a/0x30
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&dev_instance_lock_key);
lock(&dev_instance_lock_key#3);
lock(&dev_instance_lock_key);
lock(&dev_instance_lock_key#3);
*** DEADLOCK ***
locks held by kworker/u8:3/5652: 6, last CPU#1:
#0: ffff8881012d5940 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630
#1: ffffc9000481fc40 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630
#2: ffffffff90244f08 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf5/0x810
#3: ffffffff90253760 (rtnl_mutex){+.+.}-{4:4}, at: default_device_exit_batch+0xd0/0x760
#4: ffff888120c40e70 (&dev_instance_lock_key#3){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
#5: ffff88816d8dae70 (&dev_instance_lock_key){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
stack backtrace:
CPU: 1 UID: 0 PID: 5652 Comm: kworker/u8:3 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: netns cleanup_net
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150
print_circular_bug+0x2e2/0x300
check_noncircular+0x12f/0x150
__lock_acquire+0x164c/0x2de0
lock_acquire+0x115/0x350
__mutex_lock+0x19d/0x1550
unregister_netdevice_many_notify+0x5bb/0x2140
default_device_exit_batch+0x6d4/0x760
ops_undo_list+0x4b4/0x8d0
cleanup_net+0x572/0x810
process_scheduled_works+0xc3d/0x1630
worker_thread+0xa47/0xfb0
kthread+0x38b/0x480
ret_from_fork+0x514/0xb70
ret_from_fork_asm+0x1a/0x30
</TASK>
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a fix for this bug, please reply with `#syz test`
(on a separate line) and attach the patch to the email.
Notes:
- The patch will be applied on top of the tested series (as an
incremental fix).
- To test a new version of the whole series, please send it directly
to syzbot@lists.linux.dev.
- Arguments like custom git repos and branches are not supported.
The email will later be sent to:
[andrew@lunn.ch davem@davemloft.net edumazet@google.com horms@kernel.org kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [moderation/CI] Re: net: opt loopback into instance locking
2026-09-23 23:45 syzbot ci
@ 2026-09-24 2:39 ` Aleksandr Nogikh
0 siblings, 0 replies; 4+ messages in thread
From: Aleksandr Nogikh @ 2026-09-24 2:39 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Wed, Sep 23, 2026 at 7:45 PM syzbot ci
<syzbot+ci2e26614b55697582@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v2] net: opt loopback into instance locking
> https://lore.kernel.org/all/20260921190452.1467853-1-kuba@kernel.org
> * [PATCH net-next v2] net: opt loopback into instance locking
>
> and found the following issue:
> possible deadlock in default_device_exit_batch
>
> Full report is available here:
> https://ci.syzbot.org/series/23f51d46-5d1a-4839-a0a8-35d88361ffdb
>
> ***
>
> possible deadlock in default_device_exit_batch
>
> tree: net-next
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net-next.git
> base: 944ae66642b726bd6b25ae71b1e9ff88a0e0bdb0
> arch: amd64
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> config: https://ci.syzbot.org/builds/014063b0-7001-43f1-aa04-57649607febc/config
> AI triage: https://ci.syzbot.org/findings/6bb35d14-7fe7-4d73-9528-891c80cf7f1c/triage_trajectory
>
> batman_adv: batadv0: Removing interface: batadv_slave_0
> batman_adv: batadv0: Removing interface: batadv_slave_1
> ======================================================
> WARNING: possible circular locking dependency detected
> syzkaller #0 Not tainted
> ------------------------------------------------------
> kworker/u8:3/5652 is trying to acquire lock:
> ffff88811671ae70 (&dev_instance_lock_key#3){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
>
> but task is already holding lock:
> ffff88816d8dae70 (&dev_instance_lock_key){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
>
> which lock already depends on the new lock.
>
>
> the existing dependency chain (in reverse order) is:
>
> -> #1 (&dev_instance_lock_key){+.+.}-{4:4}:
> __mutex_lock+0x19d/0x1550
> unregister_netdevice_many_notify+0x5bb/0x2140
> default_device_exit_batch+0x6d4/0x760
> ops_undo_list+0x4b4/0x8d0
> cleanup_net+0x572/0x810
> process_scheduled_works+0xc3d/0x1630
> worker_thread+0xa47/0xfb0
> kthread+0x38b/0x480
> ret_from_fork+0x514/0xb70
> ret_from_fork_asm+0x1a/0x30
>
> -> #0 (&dev_instance_lock_key#3){+.+.}-{4:4}:
> __lock_acquire+0x164c/0x2de0
> lock_acquire+0x115/0x350
> __mutex_lock+0x19d/0x1550
> unregister_netdevice_many_notify+0x5bb/0x2140
> default_device_exit_batch+0x6d4/0x760
> ops_undo_list+0x4b4/0x8d0
> cleanup_net+0x572/0x810
> process_scheduled_works+0xc3d/0x1630
> worker_thread+0xa47/0xfb0
> kthread+0x38b/0x480
> ret_from_fork+0x514/0xb70
> ret_from_fork_asm+0x1a/0x30
>
> other info that might help us debug this:
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(&dev_instance_lock_key);
> lock(&dev_instance_lock_key#3);
> lock(&dev_instance_lock_key);
> lock(&dev_instance_lock_key#3);
>
> *** DEADLOCK ***
>
> locks held by kworker/u8:3/5652: 6, last CPU#1:
> #0: ffff8881012d5940 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630
> #1: ffffc9000481fc40 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630
> #2: ffffffff90244f08 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf5/0x810
> #3: ffffffff90253760 (rtnl_mutex){+.+.}-{4:4}, at: default_device_exit_batch+0xd0/0x760
> #4: ffff888120c40e70 (&dev_instance_lock_key#3){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
> #5: ffff88816d8dae70 (&dev_instance_lock_key){+.+.}-{4:4}, at: unregister_netdevice_many_notify+0x5bb/0x2140
>
> stack backtrace:
> CPU: 1 UID: 0 PID: 5652 Comm: kworker/u8:3 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> Workqueue: netns cleanup_net
> Call Trace:
> <TASK>
> dump_stack_lvl+0xe8/0x150
> print_circular_bug+0x2e2/0x300
> check_noncircular+0x12f/0x150
> __lock_acquire+0x164c/0x2de0
> lock_acquire+0x115/0x350
> __mutex_lock+0x19d/0x1550
> unregister_netdevice_many_notify+0x5bb/0x2140
> default_device_exit_batch+0x6d4/0x760
> ops_undo_list+0x4b4/0x8d0
> cleanup_net+0x572/0x810
> process_scheduled_works+0xc3d/0x1630
> worker_thread+0xa47/0xfb0
> kthread+0x38b/0x480
> ret_from_fork+0x514/0xb70
> ret_from_fork_asm+0x1a/0x30
> </TASK>
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> To test a fix for this bug, please reply with `#syz test`
> (on a separate line) and attach the patch to the email.
>
> Notes:
> - The patch will be applied on top of the tested series (as an
> incremental fix).
> - To test a new version of the whole series, please send it directly
> to syzbot@lists.linux.dev.
> - Arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [andrew@lunn.ch davem@davemloft.net edumazet@google.com horms@kernel.org kuba@kernel.org netdev@vger.kernel.org pabeni@redhat.com]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6ab46495.fb6b21f1.1b3075.0006.GAE%40google.com.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-09-24 2:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-21 3:11 [moderation/CI] Re: net: opt loopback into instance locking syzbot ci
2026-09-21 3:21 ` Aleksandr Nogikh
-- strict thread matches above, loose matches on Subject: below --
2026-09-23 23:45 syzbot ci
2026-09-24 2:39 ` Aleksandr Nogikh
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.