syzbot


possible deadlock in nr_rt_ioctl (2)

Status: upstream: reported on 2025/08/08 06:53
Reported-by: syzbot+e3a75b5d6afeb23f38be@syzkaller.appspotmail.com
First crash: 12d, last: 12d
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in nr_rt_ioctl (2) 4 1 24d 24d 0/3 upstream: reported on 2025/07/27 03:08
upstream possible deadlock in nr_rt_ioctl (2) hams 4 syz 1082 3h22m 54d 0/29 upstream: reported syz repro on 2025/06/26 13:33
upstream possible deadlock in nr_rt_ioctl hams 4 C inconclusive 8 444d 472d 25/29 fixed on 2024/06/07 18:10
linux-6.1 possible deadlock in nr_rt_ioctl 4 14 146d 229d 0/3 auto-obsoleted due to no activity on 2025/06/23 02:14
linux-5.15 possible deadlock in nr_rt_ioctl 4 6 146d 181d 0/3 auto-obsoleted due to no activity on 2025/07/04 21:31

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
5.15.189-syzkaller #0 Not tainted
------------------------------------------------------
syz.3.1428/11152 is trying to acquire lock:
ffffffff8d36d418 (nr_neigh_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
ffffffff8d36d418 (nr_neigh_list_lock){+...}-{2:2}, at: nr_remove_neigh net/netrom/nr_route.c:307 [inline]
ffffffff8d36d418 (nr_neigh_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:472 [inline]
ffffffff8d36d418 (nr_neigh_list_lock){+...}-{2:2}, at: nr_rt_ioctl+0x38d/0xce0 net/netrom/nr_route.c:692

but task is already holding lock:
ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_node_lock include/net/netrom.h:151 [inline]
ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:459 [inline]
ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_rt_ioctl+0x190/0xce0 net/netrom/nr_route.c:692

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&nr_node->node_lock){+...}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
       _raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:368 [inline]
       nr_node_lock include/net/netrom.h:151 [inline]
       nr_dec_obs net/netrom/nr_route.c:459 [inline]
       nr_rt_ioctl+0x190/0xce0 net/netrom/nr_route.c:692
       sock_do_ioctl+0xd3/0x2f0 net/socket.c:1140
       sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (nr_node_list_lock){+...}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
       _raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:368 [inline]
       nr_rt_device_down+0xa5/0x710 net/netrom/nr_route.c:517
       nr_device_event+0x133/0x140 net/netrom/af_netrom.c:126
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xcb/0x160 kernel/notifier.c:391
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       __dev_notify_flags+0x178/0x2d0 net/core/dev.c:-1
       dev_change_flags+0xe3/0x1a0 net/core/dev.c:8929
       dev_ifsioc+0x147/0xe70 net/core/dev_ioctl.c:324
       dev_ioctl+0x55f/0xe50 net/core/dev_ioctl.c:587
       sock_do_ioctl+0x222/0x2f0 net/socket.c:1154
       sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (nr_neigh_list_lock){+...}-{2:2}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
       _raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:368 [inline]
       nr_remove_neigh net/netrom/nr_route.c:307 [inline]
       nr_dec_obs net/netrom/nr_route.c:472 [inline]
       nr_rt_ioctl+0x38d/0xce0 net/netrom/nr_route.c:692
       sock_do_ioctl+0xd3/0x2f0 net/socket.c:1140
       sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

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

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

2 locks held by syz.3.1428/11152:
 #0: ffffffff8d36d478 (nr_node_list_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
 #0: ffffffff8d36d478 (nr_node_list_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:457 [inline]
 #0: ffffffff8d36d478 (nr_node_list_lock){+...}-{2:2}, at: nr_rt_ioctl+0x101/0xce0 net/netrom/nr_route.c:692
 #1: ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:368 [inline]
 #1: ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_node_lock include/net/netrom.h:151 [inline]
 #1: ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_dec_obs net/netrom/nr_route.c:459 [inline]
 #1: ffff8881441af770 (&nr_node->node_lock){+...}-{2:2}, at: nr_rt_ioctl+0x190/0xce0 net/netrom/nr_route.c:692

stack backtrace:
CPU: 0 PID: 11152 Comm: syz.3.1428 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
 _raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
 spin_lock_bh include/linux/spinlock.h:368 [inline]
 nr_remove_neigh net/netrom/nr_route.c:307 [inline]
 nr_dec_obs net/netrom/nr_route.c:472 [inline]
 nr_rt_ioctl+0x38d/0xce0 net/netrom/nr_route.c:692
 sock_do_ioctl+0xd3/0x2f0 net/socket.c:1140
 sock_ioctl+0x4ed/0x6e0 net/socket.c:1257
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f649f72fbe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f649d976038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f649f957090 RCX: 00007f649f72fbe9
RDX: 0000000000000000 RSI: 00000000000089e2 RDI: 000000000000000a
RBP: 00007f649f7b2e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f649f957128 R14: 00007f649f957090 R15: 00007fff0a8cadb8
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/08 06:52 linux-5.15.y c79648372d02 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in nr_rt_ioctl
* Struck through repros no longer work on HEAD.