syzbot


possible deadlock in smc_release

Status: upstream: reported C repro on 2024/09/24 05:56
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+793d678d565a6f4300f4@syzkaller.appspotmail.com
First crash: 143d, last: 5d20h
Bug presence (3)
Date Name Commit Repro Result
2024/11/09 linux-5.15.y (ToT) 3c17fc483905 C [report] possible deadlock in smc_release
2024/09/24 upstream (ToT) abf2050f51fd C [report] possible deadlock in smc_release
2024/11/09 upstream (ToT) da4373fbcf00 C Didn't crash
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in smc_release net s390 C error done 60 4d17h 378d 0/28 upstream: reported C repro on 2024/02/02 13:26
linux-6.1 possible deadlock in smc_release origin:upstream missing-backport C 215 5d18h 382d 0/3 upstream: reported C repro on 2024/01/29 16:17

Sample crash report:
netdevsim netdevsim0 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0
======================================================
WARNING: possible circular locking dependency detected
5.15.176-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor350/4019 is trying to acquire lock:
ffff0000ce101450 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0xd0/0x1c0 kernel/workqueue.c:3090

but task is already holding lock:
ffff0000ce100120 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1f4/0x574

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (sk_lock-AF_SMC/1){+.+.}-{0:0}:
       lock_sock_nested+0xec/0x1ec net/core/sock.c:3253
       smc_listen_out+0x11c/0x3fc net/smc/af_smc.c:1524
       smc_listen_work+0x1f4/0xe6c
       process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
       worker_thread+0x910/0x1034 kernel/workqueue.c:2457
       kthread+0x37c/0x45c kernel/kthread.c:334
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870

-> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}:
       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+0x32d4/0x7638 kernel/locking/lockdep.c:5012
       lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
       __flush_work+0xf8/0x1c0 kernel/workqueue.c:3090
       __cancel_work_timer+0x3ec/0x548 kernel/workqueue.c:3181
       cancel_work_sync+0x24/0x38 kernel/workqueue.c:3217
       smc_clcsock_release+0x64/0xec net/smc/smc_close.c:29
       __smc_release+0x388/0x540 net/smc/af_smc.c:211
       smc_close_non_accepted+0xdc/0x298 net/smc/af_smc.c:1466
       smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
       smc_close_active+0x908/0xc8c net/smc/smc_close.c:219
       __smc_release+0x9c/0x540 net/smc/af_smc.c:187
       smc_release+0x26c/0x574 net/smc/af_smc.c:254
       __sock_release net/socket.c:649 [inline]
       sock_close+0xb8/0x1fc net/socket.c:1336
       __fput+0x1c4/0x800 fs/file_table.c:280
       ____fput+0x20/0x30 fs/file_table.c:308
       task_work_run+0x130/0x1e4 kernel/task_work.c:188
       exit_task_work include/linux/task_work.h:33 [inline]
       do_exit+0x670/0x20bc kernel/exit.c:874
       do_group_exit+0x110/0x268 kernel/exit.c:996
       __do_sys_exit_group kernel/exit.c:1007 [inline]
       __se_sys_exit_group kernel/exit.c:1005 [inline]
       __wake_up_parent+0x0/0x60 kernel/exit.c:1005
       __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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0x84/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_SMC/1);
                               lock((work_completion)(&new_smc->smc_listen_work));
                               lock(sk_lock-AF_SMC/1);
  lock((work_completion)(&new_smc->smc_listen_work));

 *** DEADLOCK ***

2 locks held by syz-executor350/4019:
 #0: ffff0000e18c7a10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #0: ffff0000e18c7a10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff0000e18c7a10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1336
 #1: ffff0000ce100120 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x1f4/0x574

stack backtrace:
CPU: 0 PID: 4019 Comm: syz-executor350 Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Call trace:
 dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2011
 check_noncircular+0x2cc/0x378 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+0x32d4/0x7638 kernel/locking/lockdep.c:5012
 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
 __flush_work+0xf8/0x1c0 kernel/workqueue.c:3090
 __cancel_work_timer+0x3ec/0x548 kernel/workqueue.c:3181
 cancel_work_sync+0x24/0x38 kernel/workqueue.c:3217
 smc_clcsock_release+0x64/0xec net/smc/smc_close.c:29
 __smc_release+0x388/0x540 net/smc/af_smc.c:211
 smc_close_non_accepted+0xdc/0x298 net/smc/af_smc.c:1466
 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
 smc_close_active+0x908/0xc8c net/smc/smc_close.c:219
 __smc_release+0x9c/0x540 net/smc/af_smc.c:187
 smc_release+0x26c/0x574 net/smc/af_smc.c:254
 __sock_release net/socket.c:649 [inline]
 sock_close+0xb8/0x1fc net/socket.c:1336
 __fput+0x1c4/0x800 fs/file_table.c:280
 ____fput+0x20/0x30 fs/file_table.c:308
 task_work_run+0x130/0x1e4 kernel/task_work.c:188
 exit_task_work include/linux/task_work.h:33 [inline]
 do_exit+0x670/0x20bc kernel/exit.c:874
 do_group_exit+0x110/0x268 kernel/exit.c:996
 __do_sys_exit_group kernel/exit.c:1007 [inline]
 __se_sys_exit_group kernel/exit.c:1005 [inline]
 __wake_up_parent+0x0/0x60 kernel/exit.c:1005
 __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+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Crashes (222):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/23 11:05 linux-5.15.y 4735586da88e a44b0418 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/04 04:52 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2024/09/24 05:55 linux-5.15.y 3a5928702e71 89298aad .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/09 05:07 linux-5.15.y c16c81c81336 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/08 02:39 linux-5.15.y c16c81c81336 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/08 02:39 linux-5.15.y c16c81c81336 ef44b750 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/07 18:25 linux-5.15.y c16c81c81336 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/07 03:14 linux-5.15.y c16c81c81336 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/06 23:04 linux-5.15.y c16c81c81336 8002dd28 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/06 12:54 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/06 12:52 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/06 07:24 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/05 20:57 linux-5.15.y c16c81c81336 4dc70884 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/05 08:44 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/05 04:42 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/30 07:19 linux-5.15.y 003148680b79 afe4eff5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/29 18:14 linux-5.15.y 003148680b79 136953f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/28 21:53 linux-5.15.y 003148680b79 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/24 12:48 linux-5.15.y 003148680b79 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/24 04:16 linux-5.15.y 003148680b79 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/23 08:59 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/23 01:37 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/18 12:17 linux-5.15.y 4735586da88e f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/17 17:25 linux-5.15.y 4735586da88e 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/17 10:19 linux-5.15.y 4735586da88e f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/17 10:17 linux-5.15.y 4735586da88e f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/14 23:40 linux-5.15.y 4735586da88e f310a27d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/12 22:54 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/01/12 15:38 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in smc_release
2025/02/07 14:06 linux-5.15.y c16c81c81336 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/07 12:44 linux-5.15.y c16c81c81336 53657d1b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/06 11:24 linux-5.15.y c16c81c81336 577d049b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/05 10:29 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/05 05:56 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/05 04:23 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/02/02 23:43 linux-5.15.y c16c81c81336 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/30 00:49 linux-5.15.y 003148680b79 136953f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/29 09:54 linux-5.15.y 003148680b79 865ef71e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/28 18:15 linux-5.15.y 003148680b79 f5427d7c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/25 02:14 linux-5.15.y 003148680b79 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/24 21:12 linux-5.15.y 003148680b79 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/24 19:49 linux-5.15.y 003148680b79 1293872d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/24 01:00 linux-5.15.y 003148680b79 521b0ce3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/23 10:05 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/22 22:30 linux-5.15.y 4735586da88e a44b0418 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/17 01:44 linux-5.15.y 4735586da88e f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
2025/01/12 05:44 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in smc_release
* Struck through repros no longer work on HEAD.