syzbot


possible deadlock in rtnl_lock

Status: upstream: reported on 2025/03/07 23:48
Reported-by: syzbot+8d3fcc0190951c1256dd@syzkaller.appspotmail.com
First crash: 106d, last: 4d04h
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-44 possible deadlock in rtnl_lock C 4676 2070d 2263d 0/2 public: reported C repro on 2019/04/12 00:00
upstream possible deadlock in rtnl_lock (5) net C 1009 2615d 2643d 5/29 fixed on 2018/05/08 18:30
upstream possible deadlock in rtnl_lock (3) net C 3633 2691d 2692d 4/29 fixed on 2018/02/07 13:48
linux-4.19 possible deadlock in rtnl_lock C error 31 1744d 1994d 0/1 upstream: reported C repro on 2020/01/06 01:18
upstream possible deadlock in rtnl_lock (4) net C 73333 2674d 2691d 4/29 fixed on 2018/02/26 20:04
upstream possible deadlock in rtnl_lock (6) net C done error 551 1933d 2175d 0/29 auto-obsoleted due to no activity on 2022/12/21 11:47
android-49 possible deadlock in rtnl_lock C 2906 2493d 2644d 0/3 closed as invalid on 2019/04/05 05:43
upstream possible deadlock in rtnl_lock net C 15711 2698d 2754d 4/29 fixed on 2018/02/01 04:00
upstream possible deadlock in rtnl_lock (2) net C 10369 2694d 2697d 4/29 fixed on 2018/02/04 23:45
linux-4.14 possible deadlock in rtnl_lock C inconclusive 312 1852d 1994d 0/1 upstream: reported C repro on 2020/01/06 01:45
upstream possible deadlock in rtnl_lock (8) net C 434 54d 307d 0/29 upstream: reported C repro on 2024/08/19 03:49

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
5.15.185-syzkaller #0 Not tainted
------------------------------------------------------
syz.5.636/6327 is trying to acquire lock:
ffff8000162886e8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72

but task is already holding lock:
ffff0000e8695120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
ffff0000e8695120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x274/0xa5c net/ax25/af_ax25.c:570

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (sk_lock-AF_AX25){+.+.}-{0:0}:
       lock_sock_nested+0xd8/0x1d4 net/core/sock.c:3251
       lock_sock include/net/sock.h:1694 [inline]
       ax25_kill_by_device net/ax25/af_ax25.c:99 [inline]
       ax25_device_event+0x20c/0x590 net/ax25/af_ax25.c:142
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
       call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       dev_close_many+0x2cc/0x440 net/core/dev.c:1650
       dev_close+0x148/0x1f8 net/core/dev.c:1672
       bpq_device_event+0x318/0x824 drivers/net/hamradio/bpqether.c:548
       notifier_call_chain kernel/notifier.c:83 [inline]
       raw_notifier_call_chain+0xd4/0x164 kernel/notifier.c:391
       call_netdevice_notifiers_info net/core/dev.c:2049 [inline]
       call_netdevice_notifiers_extack net/core/dev.c:2061 [inline]
       call_netdevice_notifiers net/core/dev.c:2075 [inline]
       dev_close_many+0x2cc/0x440 net/core/dev.c:1650
       dev_close+0x148/0x1f8 net/core/dev.c:1672
       bond_setup_by_slave+0x70/0x318 drivers/net/bonding/bond_main.c:1471
       bond_enslave+0x624/0x3014 drivers/net/bonding/bond_main.c:1855
       bond_do_ioctl+0x6ec/0xb3c drivers/net/bonding/bond_main.c:4238
       dev_siocbond net/core/dev_ioctl.c:270 [inline]
       dev_ifsioc+0xc44/0xef4 net/core/dev_ioctl.c:417
       dev_ioctl+0x4d0/0xc94 net/core/dev_ioctl.c:587
       sock_do_ioctl+0x18c/0x240 net/socket.c:1154
       sock_ioctl+0x5c8/0x87c net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl fs/ioctl.c:860 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #0 (rtnl_mutex){+.+.}-{3:3}:
       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+0x2928/0x651c kernel/locking/lockdep.c:5012
       lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743
       rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72
       ax25_setsockopt+0x870/0xa5c net/ax25/af_ax25.c:676
       __sys_setsockopt+0x2f8/0x4b0 net/socket.c:2203
       __do_sys_setsockopt net/socket.c:2214 [inline]
       __se_sys_setsockopt net/socket.c:2211 [inline]
       __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2211
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(sk_lock-AF_AX25);
                               lock(rtnl_mutex);
                               lock(sk_lock-AF_AX25);
  lock(rtnl_mutex);

 *** DEADLOCK ***

1 lock held by syz.5.636/6327:
 #0: ffff0000e8695120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1694 [inline]
 #0: ffff0000e8695120 (sk_lock-AF_AX25){+.+.}-{0:0}, at: ax25_setsockopt+0x274/0xa5c net/ax25/af_ax25.c:570

stack backtrace:
CPU: 1 PID: 6327 Comm: syz.5.636 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __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:2011
 check_noncircular+0x240/0x2d4 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+0x2928/0x651c kernel/locking/lockdep.c:5012
 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x194/0x1edc kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743
 rtnl_lock+0x20/0x2c net/core/rtnetlink.c:72
 ax25_setsockopt+0x870/0xa5c net/ax25/af_ax25.c:676
 __sys_setsockopt+0x2f8/0x4b0 net/socket.c:2203
 __do_sys_setsockopt net/socket.c:2214 [inline]
 __se_sys_setsockopt net/socket.c:2211 [inline]
 __arm64_sys_setsockopt+0xb8/0xd4 net/socket.c:2211
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Crashes (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/18 04:54 linux-5.15.y 1c700860e8bc e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/18 04:54 linux-5.15.y 1c700860e8bc e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/18 04:54 linux-5.15.y 1c700860e8bc e77fae15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/17 07:53 linux-5.15.y 1c700860e8bc cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/14 07:06 linux-5.15.y 1c700860e8bc 0e8da31f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/13 07:40 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/06/13 04:32 linux-5.15.y 1c700860e8bc 98683f8f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/05/31 20:19 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/05/31 03:34 linux-5.15.y 98f47d0e9b8c 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/05/28 08:18 linux-5.15.y 98f47d0e9b8c 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/05/26 14:12 linux-5.15.y 98f47d0e9b8c 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/04/13 12:29 linux-5.15.y f7347f400572 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/04/13 08:42 linux-5.15.y f7347f400572 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/04/04 00:21 linux-5.15.y 0c935c049b5c d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/04/04 00:21 linux-5.15.y 0c935c049b5c d7ae3a11 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
2025/03/07 23:47 linux-5.15.y c16c81c81336 7e3bd60d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rtnl_lock
* Struck through repros no longer work on HEAD.