syzbot


possible deadlock in sockopt_lock_sock

Status: upstream: reported C repro on 2024/08/15 10:13
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+819a360379cf16b5f0d3@syzkaller.appspotmail.com
First crash: 278d, last: 29d
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly net report (Apr 2025) 0 (1) 2025/04/09 07:11
[syzbot] [net?] possible deadlock in sockopt_lock_sock 0 (2) 2024/10/09 12:50
Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/05/01 18:31 23m retest repro upstream OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.15.0-rc2-syzkaller-00087-gcfb2e2c57aef #0 Not tainted
------------------------------------------------------
syz.2.816/9515 is trying to acquire lock:
ffff8880347cb198 (sk_lock-AF_INET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1651 [inline]
ffff8880347cb198 (sk_lock-AF_INET){+.+.}-{0:0}, at: sockopt_lock_sock net/core/sock.c:1148 [inline]
ffff8880347cb198 (sk_lock-AF_INET){+.+.}-{0:0}, at: sockopt_lock_sock+0x54/0x70 net/core/sock.c:1139

but task is already holding lock:
ffffffff9012e7e8 (rtnl_mutex){+.+.}-{4:4}, at: do_ip_getsockopt+0x1843/0x2220 net/ipv4/ip_sockglue.c:1702

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (rtnl_mutex){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       do_ipv6_setsockopt+0x2042/0x4420 net/ipv6/ipv6_sockglue.c:566
       ipv6_setsockopt+0xcb/0x170 net/ipv6/ipv6_sockglue.c:993
       tcp_setsockopt+0xa4/0x100 net/ipv4/tcp.c:4077
       smc_setsockopt+0x1b3/0xa00 net/smc/af_smc.c:3081
       do_sock_setsockopt+0x221/0x470 net/socket.c:2296
       __sys_setsockopt+0x1a0/0x230 net/socket.c:2321
       __do_sys_setsockopt net/socket.c:2327 [inline]
       __se_sys_setsockopt net/socket.c:2324 [inline]
       __x64_sys_setsockopt+0xbd/0x160 net/socket.c:2324
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&smc->clcsock_release_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       smc_switch_to_fallback+0x2d/0x9f0 net/smc/af_smc.c:903
       smc_sendmsg+0x13d/0x520 net/smc/af_smc.c:2781
       sock_sendmsg_nosec net/socket.c:712 [inline]
       __sock_sendmsg net/socket.c:727 [inline]
       ____sys_sendmsg+0xa95/0xc70 net/socket.c:2566
       ___sys_sendmsg+0x134/0x1d0 net/socket.c:2620
       __sys_sendmsg+0x16d/0x220 net/socket.c:2652
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (sk_lock-AF_INET){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain kernel/locking/lockdep.c:3909 [inline]
       __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
       lock_acquire kernel/locking/lockdep.c:5866 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
       lock_sock_nested+0x41/0xf0 net/core/sock.c:3702
       lock_sock include/net/sock.h:1651 [inline]
       sockopt_lock_sock net/core/sock.c:1148 [inline]
       sockopt_lock_sock+0x54/0x70 net/core/sock.c:1139
       do_ip_getsockopt+0x13e4/0x2220 net/ipv4/ip_sockglue.c:1703
       ip_getsockopt+0x9b/0x1e0 net/ipv4/ip_sockglue.c:1765
       raw_getsockopt+0x4d/0x1f0 net/ipv4/raw.c:865
       do_sock_getsockopt+0x3fc/0x800 net/socket.c:2357
       __sys_getsockopt+0x12f/0x260 net/socket.c:2386
       __do_sys_getsockopt net/socket.c:2393 [inline]
       __se_sys_getsockopt net/socket.c:2390 [inline]
       __x64_sys_getsockopt+0xbd/0x160 net/socket.c:2390
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  sk_lock-AF_INET --> &smc->clcsock_release_lock --> rtnl_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(rtnl_mutex);
                               lock(&smc->clcsock_release_lock);
                               lock(rtnl_mutex);
  lock(sk_lock-AF_INET);

 *** DEADLOCK ***

1 lock held by syz.2.816/9515:
 #0: ffffffff9012e7e8 (rtnl_mutex){+.+.}-{4:4}, at: do_ip_getsockopt+0x1843/0x2220 net/ipv4/ip_sockglue.c:1702

stack backtrace:
CPU: 0 UID: 0 PID: 9515 Comm: syz.2.816 Not tainted 6.15.0-rc2-syzkaller-00087-gcfb2e2c57aef #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2079
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2211
 check_prev_add kernel/locking/lockdep.c:3166 [inline]
 check_prevs_add kernel/locking/lockdep.c:3285 [inline]
 validate_chain kernel/locking/lockdep.c:3909 [inline]
 __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
 lock_acquire kernel/locking/lockdep.c:5866 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
 lock_sock_nested+0x41/0xf0 net/core/sock.c:3702
 lock_sock include/net/sock.h:1651 [inline]
 sockopt_lock_sock net/core/sock.c:1148 [inline]
 sockopt_lock_sock+0x54/0x70 net/core/sock.c:1139
 do_ip_getsockopt+0x13e4/0x2220 net/ipv4/ip_sockglue.c:1703
 ip_getsockopt+0x9b/0x1e0 net/ipv4/ip_sockglue.c:1765
 raw_getsockopt+0x4d/0x1f0 net/ipv4/raw.c:865
 do_sock_getsockopt+0x3fc/0x800 net/socket.c:2357
 __sys_getsockopt+0x12f/0x260 net/socket.c:2386
 __do_sys_getsockopt net/socket.c:2393 [inline]
 __se_sys_getsockopt net/socket.c:2390 [inline]
 __x64_sys_getsockopt+0xbd/0x160 net/socket.c:2390
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd8eed8e169
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:00007fd8efb46038 EFLAGS: 00000246 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00007fd8eefb5fa0 RCX: 00007fd8eed8e169
RDX: 0000000000000030 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 00007fd8eee10a68 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fd8eefb5fa0 R15: 00007ffcc9fd3988
 </TASK>

Crashes (3397):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/17 18:12 upstream cfb2e2c57aef 552876f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/17 14:32 upstream cfb2e2c57aef 552876f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/17 01:28 upstream c62f4b82d571 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/17 00:10 upstream c62f4b82d571 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/16 22:54 upstream c62f4b82d571 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/16 21:21 upstream c62f4b82d571 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/16 15:00 upstream 1a1d569a75f3 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/16 09:18 upstream 1a1d569a75f3 a95239b1 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/15 15:42 upstream 834a4a689699 85125322 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/15 06:13 upstream 834a4a689699 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/15 03:26 upstream 834a4a689699 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/14 17:43 upstream 8ffd015db85f 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/14 15:24 upstream 8ffd015db85f 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/14 14:29 upstream 8ffd015db85f 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/14 11:08 upstream 8ffd015db85f 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 21:49 upstream 5aaaedb0cb54 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 18:38 upstream 5aaaedb0cb54 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 12:53 upstream 7cdabafc0012 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 11:43 upstream 7cdabafc0012 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in sockopt_lock_sock
2025/04/13 09:09 upstream 7cdabafc0012 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 06:18 upstream 7cdabafc0012 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 03:23 upstream 7cdabafc0012 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/13 01:17 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/12 23:53 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/12 16:40 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in sockopt_lock_sock
2025/04/12 13:39 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/12 13:39 upstream 3bde70a2c827 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/12 06:37 upstream e618ee89561b 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/12 00:07 upstream e618ee89561b 0bd6db41 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/11 22:22 upstream 900241a5cc15 12ba9c21 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/11 17:33 upstream 900241a5cc15 12ba9c21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/11 12:52 upstream 900241a5cc15 12ba9c21 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/11 10:32 upstream 0c7cae12f67c 94486846 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/11 08:36 upstream 0c7cae12f67c 94486846 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/11 06:56 upstream 0c7cae12f67c 94486846 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/11 06:42 upstream 0c7cae12f67c 94486846 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/10 09:45 upstream 3b07108ada81 988b336c .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/09 08:05 upstream bec7dcbc242c b133e63a .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/09 06:09 upstream bec7dcbc242c b133e63a .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/09 05:08 upstream bec7dcbc242c b133e63a .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/08 18:56 upstream 0af2f6be1b42 a775275d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/08 07:31 upstream 0af2f6be1b42 a2ada0e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/08 04:13 upstream 0af2f6be1b42 a2ada0e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/08 01:09 upstream 0af2f6be1b42 a2ada0e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/04/07 19:37 upstream 0af2f6be1b42 2f0c9720 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2025/04/07 08:32 upstream 0af2f6be1b42 1c65791e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2024/10/09 12:49 upstream 75b607fab38d 56fb2cb7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in sockopt_lock_sock
2024/08/12 00:54 upstream cb2e5ee8e7a0 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sockopt_lock_sock
2025/03/09 20:19 upstream 1110ce6a1e34 163f510d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in sockopt_lock_sock
2025/04/17 04:30 upstream c62f4b82d571 a95239b1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/04/14 07:36 upstream 004a365eb8b9 0bd6db41 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64-compat possible deadlock in sockopt_lock_sock
2025/04/13 16:53 upstream 5aaaedb0cb54 0bd6db41 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/04/12 01:30 upstream e618ee89561b 0bd6db41 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/04/10 08:29 upstream 3b07108ada81 988b336c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/04/08 16:28 upstream 0af2f6be1b42 a775275d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/04/07 22:28 upstream 0af2f6be1b42 a2ada0e7 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/01/16 13:14 upstream 619f0b6fad52 968edaf4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm64 possible deadlock in sockopt_lock_sock
2024/08/11 10:09 upstream 5189dafa4cf9 6f4edef4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sockopt_lock_sock
2025/01/11 11:23 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes 6f6ecce59d99 6dbc6a9b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 possible deadlock in sockopt_lock_sock
* Struck through repros no longer work on HEAD.