syzbot


possible deadlock in nr_rt_device_down

Status: upstream: reported C repro on 2025/01/01 09:10
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+473934ecefcd67e643fb@syzkaller.appspotmail.com
First crash: 157d, last: 8d07h
Bug presence (1)
Date Name Commit Repro Result
2025/05/31 upstream (ToT) 0f70f5b08a47 C [report] possible deadlock in nr_del_node
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in nr_rt_device_down (2) hams 2 315d 315d 0/28 closed as invalid on 2024/09/04 18:18
upstream possible deadlock in nr_rt_device_down (3) hams C error 4111 1d03h 265d 0/28 upstream: reported C repro on 2024/09/14 18:32
linux-5.15 possible deadlock in nr_rt_device_down origin:upstream C error 54 20d 391d 0/3 upstream: reported C repro on 2024/05/12 01:54

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.1.139-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor304/4336 is trying to acquire lock:
ffff80001781da18 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]
ffff80001781da18 (nr_node_list_lock){+...}-{2:2}, at: nr_rt_device_down+0xb4/0x660 net/netrom/nr_route.c:517

but task is already holding lock:
ffff80001781d9b8 (nr_neigh_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]
ffff80001781d9b8 (nr_neigh_list_lock){+...}-{2:2}, at: nr_rt_device_down+0x38/0x660 net/netrom/nr_route.c:514

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (nr_neigh_list_lock){+...}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x54/0x6c kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:356 [inline]
       nr_remove_neigh net/netrom/nr_route.c:307 [inline]
       nr_del_node+0x35c/0x878 net/netrom/nr_route.c:342
       nr_rt_ioctl+0x820/0xb80 net/netrom/nr_route.c:678
       nr_ioctl+0x1c4/0x4e4 net/netrom/af_netrom.c:1254
       sock_do_ioctl+0xf8/0x240 net/socket.c:1204
       sock_ioctl+0x5c4/0x840 net/socket.c:1321
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #1 (&nr_node->node_lock){+...}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x54/0x6c kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:356 [inline]
       nr_node_lock include/net/netrom.h:152 [inline]
       nr_del_node+0xbc/0x878 net/netrom/nr_route.c:335
       nr_rt_ioctl+0x820/0xb80 net/netrom/nr_route.c:678
       nr_ioctl+0x1c4/0x4e4 net/netrom/af_netrom.c:1254
       sock_do_ioctl+0xf8/0x240 net/socket.c:1204
       sock_ioctl+0x5c4/0x840 net/socket.c:1321
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #0 (nr_node_list_lock){+...}-{2:2}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049
       lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x54/0x6c kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:356 [inline]
       nr_rt_device_down+0xb4/0x660 net/netrom/nr_route.c:517
       nr_device_event+0x138/0x164 net/netrom/af_netrom.c:126
       notifier_call_chain kernel/notifier.c:87 [inline]
       raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:455
       call_netdevice_notifiers_info net/core/dev.c:2001 [inline]
       call_netdevice_notifiers_extack net/core/dev.c:2039 [inline]
       call_netdevice_notifiers net/core/dev.c:2053 [inline]
       __dev_notify_flags+0x250/0x46c net/core/dev.c:-1
       dev_change_flags+0xc8/0x154 net/core/dev.c:8702
       dev_ifsioc+0x524/0xed0 net/core/dev_ioctl.c:327
       dev_ioctl+0x4c8/0xc8c net/core/dev_ioctl.c:588
       sock_do_ioctl+0x18c/0x240 net/socket.c:1218
       sock_ioctl+0x5c4/0x840 net/socket.c:1321
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

other info that might help us debug this:

Chain exists of:
  nr_node_list_lock --> &nr_node->node_lock --> nr_neigh_list_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(nr_neigh_list_lock);
                               lock(&nr_node->node_lock);
                               lock(nr_neigh_list_lock);
  lock(nr_node_list_lock);

 *** DEADLOCK ***

2 locks held by syz-executor304/4336:
 #0: ffff8000176d9188 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
 #1: ffff80001781d9b8 (nr_neigh_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]
 #1: ffff80001781d9b8 (nr_neigh_list_lock){+...}-{2:2}, at: nr_rt_device_down+0x38/0x660 net/netrom/nr_route.c:514

stack backtrace:
CPU: 0 PID: 4336 Comm: syz-executor304 Not tainted 6.1.139-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 dump_stack+0x1c/0x5c lib/dump_stack.c:113
 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048
 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049
 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
 _raw_spin_lock_bh+0x54/0x6c kernel/locking/spinlock.c:178
 spin_lock_bh include/linux/spinlock.h:356 [inline]
 nr_rt_device_down+0xb4/0x660 net/netrom/nr_route.c:517
 nr_device_event+0x138/0x164 net/netrom/af_netrom.c:126
 notifier_call_chain kernel/notifier.c:87 [inline]
 raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:455
 call_netdevice_notifiers_info net/core/dev.c:2001 [inline]
 call_netdevice_notifiers_extack net/core/dev.c:2039 [inline]
 call_netdevice_notifiers net/core/dev.c:2053 [inline]
 __dev_notify_flags+0x250/0x46c net/core/dev.c:-1
 dev_change_flags+0xc8/0x154 net/core/dev.c:8702
 dev_ifsioc+0x524/0xed0 net/core/dev_ioctl.c:327
 dev_ioctl+0x4c8/0xc8c net/core/dev_ioctl.c:588
 sock_do_ioctl+0x18c/0x240 net/socket.c:1218
 sock_ioctl+0x5c4/0x840 net/socket.c:1321
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Crashes (51):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/19 03:42 linux-6.1.y 325285d9fc86 f41472b0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/06 08:58 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/01 12:37 linux-6.1.y 563edd786f0a d3ccff63 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/01 09:09 linux-6.1.y 563edd786f0a d3ccff63 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/05/30 04:45 linux-6.1.y da3c5173c55f 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/05/06 01:44 linux-6.1.y ac7079a42ea5 6ca47dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/05/05 21:08 linux-6.1.y ac7079a42ea5 6ca47dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/04/18 03:49 linux-6.1.y 420102835862 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/04/06 00:02 linux-6.1.y 8e60a714ba3b 1c65791e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/04/04 14:29 linux-6.1.y 8e60a714ba3b 1c4febdb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/03/11 19:49 linux-6.1.y 6ae7ac5c4251 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/03/11 16:48 linux-6.1.y 6ae7ac5c4251 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/03/11 16:48 linux-6.1.y 6ae7ac5c4251 16256247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/22 07:45 linux-6.1.y 3a8358583626 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/20 10:53 linux-6.1.y 0cbb5f65e52f 50668798 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/20 10:53 linux-6.1.y 0cbb5f65e52f 50668798 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/03 21:41 linux-6.1.y 0cbb5f65e52f a21a8419 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/01 01:20 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/01 01:19 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/01 01:16 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/01 01:16 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/02/01 01:16 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/23 08:56 linux-6.1.y f4f677285b38 a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/23 08:56 linux-6.1.y f4f677285b38 a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/19 15:31 linux-6.1.y f4f677285b38 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/19 15:31 linux-6.1.y f4f677285b38 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/16 01:03 linux-6.1.y c63962be84ef 968edaf4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/16 01:03 linux-6.1.y c63962be84ef 968edaf4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/15 00:02 linux-6.1.y c63962be84ef f310a27d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/14 20:58 linux-6.1.y c63962be84ef f310a27d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/14 20:58 linux-6.1.y c63962be84ef f310a27d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/11 01:50 linux-6.1.y c63962be84ef 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/11 01:49 linux-6.1.y c63962be84ef 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/01/08 01:48 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in nr_rt_device_down
2025/05/02 05:26 linux-6.1.y 535ec20c5027 51b137cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/04/04 03:07 linux-6.1.y 8e60a714ba3b d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/20 11:41 linux-6.1.y 0cbb5f65e52f 50668798 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/08 13:30 linux-6.1.y 0cbb5f65e52f ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/07 13:17 linux-6.1.y 0cbb5f65e52f 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/01 17:40 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/01 17:34 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/02/01 01:52 linux-6.1.y 75cefdf153f5 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/31 04:22 linux-6.1.y 75cefdf153f5 4c6ac32f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/29 09:40 linux-6.1.y 75cefdf153f5 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/29 09:39 linux-6.1.y 75cefdf153f5 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/10 16:27 linux-6.1.y c63962be84ef 67d7ec0a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/07 14:06 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/06 06:18 linux-6.1.y 7dc732d24ff7 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
2025/01/02 22:14 linux-6.1.y 7dc732d24ff7 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in nr_rt_device_down
* Struck through repros no longer work on HEAD.