syzbot


possible deadlock in ip_mc_drop_socket (2)

Status: upstream: reported on 2024/07/08 16:15
Subsystems: net
[Documentation on labels]
Reported-by: syzbot+0a487bbdbba35360ad29@syzkaller.appspotmail.com
First crash: 264d, last: 3d17h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [net?] possible deadlock in ip_mc_drop_socket (2) 0 (1) 2024/07/08 16:15
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in ip_mc_drop_socket net 1 1459d 1458d 0/28 auto-closed as invalid on 2021/07/28 01:06

Sample crash report:
IPVS: stopping backup sync thread 19749 ...
======================================================
WARNING: possible circular locking dependency detected
6.14.0-rc7-syzkaller-00205-g586de92313fc #0 Not tainted
------------------------------------------------------
syz.2.6321/26285 is trying to acquire lock:
ffffffff8fed5f48 (rtnl_mutex){+.+.}-{4:4}, at: ip_mc_drop_socket+0x81/0x280 net/ipv4/igmp.c:2784

but task is already holding lock:
ffff888034604fa8 (&smc->clcsock_release_lock){+.+.}-{4:4}, at: smc_setsockopt+0x1c3/0xd10 net/smc/af_smc.c:3073

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&smc->clcsock_release_lock){+.+.}-{4:4}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
       __mutex_lock_common kernel/locking/mutex.c:585 [inline]
       __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730
       smc_switch_to_fallback+0x35/0xd90 net/smc/af_smc.c:903
       smc_sendmsg+0x11f/0x530 net/smc/af_smc.c:2781
       sock_sendmsg_nosec net/socket.c:718 [inline]
       __sock_sendmsg+0x223/0x270 net/socket.c:733
       __sys_sendto+0x363/0x4c0 net/socket.c:2187
       __do_sys_sendto net/socket.c:2194 [inline]
       __se_sys_sendto net/socket.c:2190 [inline]
       __x64_sys_sendto+0xde/0x100 net/socket.c:2190
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (sk_lock-AF_INET){+.+.}-{0:0}:
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
       lock_sock_nested+0x48/0x100 net/core/sock.c:3662
       do_ip_setsockopt+0x1966/0x3ae0 net/ipv4/ip_sockglue.c:1078
       ip_setsockopt+0x63/0x100 net/ipv4/ip_sockglue.c:1417
       do_sock_setsockopt+0x3b1/0x720 net/socket.c:2303
       __sys_setsockopt net/socket.c:2328 [inline]
       __do_sys_setsockopt net/socket.c:2334 [inline]
       __se_sys_setsockopt net/socket.c:2331 [inline]
       __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2331
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (rtnl_mutex){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3163 [inline]
       check_prevs_add kernel/locking/lockdep.c:3282 [inline]
       validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906
       __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228
       lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
       __mutex_lock_common kernel/locking/mutex.c:585 [inline]
       __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730
       ip_mc_drop_socket+0x81/0x280 net/ipv4/igmp.c:2784
       inet_release+0x96/0x200 net/ipv4/af_inet.c:422
       __sock_release net/socket.c:647 [inline]
       sock_release+0x84/0x150 net/socket.c:675
       stop_sync_thread+0x4e6/0x5e0 net/netfilter/ipvs/ip_vs_sync.c:2004
       do_ip_vs_set_ctl+0x4c8/0xe40 net/netfilter/ipvs/ip_vs_ctl.c:2734
       nf_setsockopt+0x297/0x2c0 net/netfilter/nf_sockopt.c:101
       smc_setsockopt+0x277/0xd10 net/smc/af_smc.c:3081
       do_sock_setsockopt+0x3b1/0x720 net/socket.c:2303
       __sys_setsockopt net/socket.c:2328 [inline]
       __do_sys_setsockopt net/socket.c:2334 [inline]
       __se_sys_setsockopt net/socket.c:2331 [inline]
       __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2331
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

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

 Possible unsafe locking scenario:

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

 *** DEADLOCK ***

1 lock held by syz.2.6321/26285:
 #0: ffff888034604fa8 (&smc->clcsock_release_lock){+.+.}-{4:4}, at: smc_setsockopt+0x1c3/0xd10 net/smc/af_smc.c:3073

stack backtrace:
CPU: 0 UID: 0 PID: 26285 Comm: syz.2.6321 Not tainted 6.14.0-rc7-syzkaller-00205-g586de92313fc #0
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+0x241/0x360 lib/dump_stack.c:120
 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2076
 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2208
 check_prev_add kernel/locking/lockdep.c:3163 [inline]
 check_prevs_add kernel/locking/lockdep.c:3282 [inline]
 validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3906
 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851
 __mutex_lock_common kernel/locking/mutex.c:585 [inline]
 __mutex_lock+0x19c/0x1010 kernel/locking/mutex.c:730
 ip_mc_drop_socket+0x81/0x280 net/ipv4/igmp.c:2784
 inet_release+0x96/0x200 net/ipv4/af_inet.c:422
 __sock_release net/socket.c:647 [inline]
 sock_release+0x84/0x150 net/socket.c:675
 stop_sync_thread+0x4e6/0x5e0 net/netfilter/ipvs/ip_vs_sync.c:2004
 do_ip_vs_set_ctl+0x4c8/0xe40 net/netfilter/ipvs/ip_vs_ctl.c:2734
 nf_setsockopt+0x297/0x2c0 net/netfilter/nf_sockopt.c:101
 smc_setsockopt+0x277/0xd10 net/smc/af_smc.c:3081
 do_sock_setsockopt+0x3b1/0x720 net/socket.c:2303
 __sys_setsockopt net/socket.c:2328 [inline]
 __do_sys_setsockopt net/socket.c:2334 [inline]
 __se_sys_setsockopt net/socket.c:2331 [inline]
 __x64_sys_setsockopt+0x1ee/0x280 net/socket.c:2331
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa631f8d169
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:00007fa632dbe038 EFLAGS: 00000246 ORIG_RAX: 0000000000000036
RAX: ffffffffffffffda RBX: 00007fa6321a5fa0 RCX: 00007fa631f8d169
RDX: 000000000000048c RSI: 0000000000000000 RDI: 0000000000000006
RBP: 00007fa63200e2a0 R08: 0000000000000018 R09: 0000000000000000
R10: 0000200000000040 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fa6321a5fa0 R15: 00007fff1aac8338
 </TASK>

Crashes (169):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/24 05:03 upstream 586de92313fc 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ip_mc_drop_socket
2025/02/25 16:15 upstream d082ecbc71e9 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/22 21:46 upstream 5cf80612d3f7 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/02/21 01:18 upstream 27eddbf34490 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/02/19 08:34 upstream 6537cfb395f3 9a14138f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/02/05 09:37 upstream 5c8c229261f1 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/02/05 03:41 upstream d009de7d5428 4baca3d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/01/20 06:10 upstream 9528d418de4d f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2025/01/19 18:33 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ip_mc_drop_socket
2024/12/28 15:27 upstream fd0584d220fe d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ip_mc_drop_socket
2024/12/26 02:12 upstream 9b2ffa6148b1 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ip_mc_drop_socket
2024/12/23 23:28 upstream 4bbf9020becb 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in ip_mc_drop_socket
2024/12/10 15:29 upstream 7cb1b4663150 cfc402b4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/12 08:03 upstream b62cef9a5c67 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in ip_mc_drop_socket
2025/01/16 13:47 upstream 619f0b6fad52 f9e07a6e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in ip_mc_drop_socket
2025/02/28 06:52 net 1e15510b71c9 6a8fcbc4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/07 09:28 net 8c817eb26230 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in ip_mc_drop_socket
2025/03/24 13:34 net-next bfc17c165835 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/23 07:14 net-next b66e19dcf684 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/23 02:43 net-next b66e19dcf684 d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/10 20:33 net-next 34c84b394890 43f51a00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/10 02:17 net-next acdefab0dcbc ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/09 15:03 net-next acdefab0dcbc ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/09 13:45 net-next acdefab0dcbc ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/08 13:53 net-next 7bca2b2d5fcc ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/07 23:51 net-next 26db4dbb7478 a4f327c2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/06 15:48 net-next 3924fa995cdf 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/05 22:48 net-next 0bea93fdbaf8 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/05 08:00 net-next 135c3c86a7ce 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/04 17:21 net-next c2933b2befe2 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/02 21:02 net-next c2933b2befe2 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/01 22:07 net-next c2933b2befe2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/01 19:40 net-next c2933b2befe2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/01 17:13 net-next c2933b2befe2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/01 05:33 net-next c2933b2befe2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/02/01 04:04 net-next c2933b2befe2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/31 19:41 net-next c2933b2befe2 aa47157c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/30 16:45 net-next 0ad9617c78ac 9c8ab845 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/30 04:04 net-next 0ad9617c78ac afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/29 07:32 net-next 0ad9617c78ac 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/28 13:16 net-next 0ad9617c78ac f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/28 07:59 net-next 0ad9617c78ac 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/27 23:52 net-next 0ad9617c78ac 18070896 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/27 03:51 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/26 20:33 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/26 18:36 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/26 15:31 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/26 03:02 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/25 12:56 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/25 08:07 net-next 0ad9617c78ac 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/23 07:21 net-next 0ad9617c78ac 9d4f14f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/22 09:47 net-next b1754a69e7be da72ac06 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/21 16:10 net-next b1754a69e7be 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/20 05:08 net-next 41c5d104f338 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/20 01:35 net-next 41c5d104f338 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/19 10:11 net-next 41c5d104f338 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2025/01/19 07:14 net-next 41c5d104f338 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2024/07/06 20:19 net-next 2f5e6395714d bc4ebbb5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in ip_mc_drop_socket
2024/12/03 23:12 linux-next f486c8aa16b8 578925bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ip_mc_drop_socket
* Struck through repros no longer work on HEAD.