possible deadlock in smc_release

Status: upstream: reported C repro on 2024/02/02 13:26
Subsystems: smc
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+621fd56ba002faba6392@syzkaller.appspotmail.com
First crash: 1009d, last: 4h52m
Cause bisection: failed (error log, bisect log)
  
✨ AI-generated root cause summary:

Lockdep detects a circular locking dependency between the SMC listening socket lock (sk_lock-AF_SMC/1) and the workqueue completion lock for smc_listen_work. When closing a listening socket, smc_release() holds lock_sock_nested(&lsmc->sk, SINGLE_DEPTH_NESTING) while smc_close_cleanup_listen() calls cancel_work_sync(&new_smc->smc_listen_work) for non-accepted child sockets; conversely, smc_listen_work() in smc_listen_out() acquires lock_sock_nested(&lsmc->sk, SINGLE_DEPTH_NESTING) while running the work item. In production builds without lockdep, this does not cause a deadlock because child sockets are only dequeued from accept_q after smc_listen_out() has already released the listener's socket lock.

▶ ▼ ✨ Full AI root cause analysis
Based on kernel commit f47d223627f8:

Root Cause Analysis

1. Functions, Structs, and Files Involved


2. Trigger Mechanism and Lock Ordering Inversion

The warning is triggered when closing an SMC listening socket (lsmc) that has unaccepted child sockets in its accept queue:

  1. Dependency #1 (work_completion(&new_smc->smc_listen_work) -> sk_lock-AF_SMC/1):

    • A worker thread runs new_smc->smc_listen_work on smc_hs_wq. Under lockdep, executing the work item takes the pseudo-lock (work_completion)(&new_smc->smc_listen_work).
    • In smc_listen_out() (net/smc/af_smc.c:1934), the worker attempts to finalize handshake processing by enqueuing the child socket to the listener:
      lock_sock_nested(&lsmc->sk, SINGLE_DEPTH_NESTING);
      if (lsmc->sk.sk_state == SMC_LISTEN) {
          smc_accept_enqueue(&lsmc->sk, newsmcsk);
          release_sock(&lsmc->sk);
      ...
      
    • Lockdep establishes the dependency edge: work_completion(&new_smc->smc_listen_work) $\to$ sk_lock-AF_SMC/1.
  2. Dependency #0 (sk_lock-AF_SMC/1 -> work_completion(&new_smc->smc_listen_work)):

    • When userspace closes the listening socket (smc_release(), net/smc/af_smc.c:353), it locks the listener socket with:
      if (sk->sk_state == SMC_LISTEN)
          lock_sock_nested(sk, SINGLE_DEPTH_NESTING);
      
    • While still holding sk_lock-AF_SMC/1 on lsmc->sk, __smc_release() calls smc_close_active(lsmc) -> smc_close_cleanup_listen(&lsmc->sk).
    • smc_close_cleanup_listen() dequeues unaccepted child sockets from lsmc->accept_q and invokes smc_close_non_accepted(child_sk) -> __smc_release(child_smc) -> smc_clcsock_release(child_smc).
    • Although __smc_release() releases the child socket lock around smc_clcsock_release(), the parent listener socket lock &lsmc->sk remains held.
    • In smc_clcsock_release() (net/smc/smc_close.c:28-29):
      if (smc->listen_smc && current_work() != &smc->smc_listen_work)
          cancel_work_sync(&smc->smc_listen_work);
      
    • cancel_work_sync() invokes __flush_work(), which waits for (work_completion)(&new_smc->smc_listen_work) to complete.
    • Lockdep detects the circular dependency: sk_lock-AF_SMC/1 $\to$ work_completion(&new_smc->smc_listen_work) $\to$ sk_lock-AF_SMC/1.

3. Runtime Consequences in Production Builds (Without Sanitizers/Lockdep)

  • Memory Corruption (MemoryCorruption: false): No memory bounds, pointers, linked lists, or reference counters are corrupted. The objects are tracked properly through normal socket reference counting (sock_hold/sock_put).
  • Information Leak (InfoLeak: "none"): No kernel memory or uninitialized buffers are copied to userspace or exposed over the network.
  • Denial of Service (RawDenialOfService: false): This warning is an artifact of lockdep classifying all instances of smc_listen_work under a single completion lock class and all listener sockets under sk_lock-AF_SMC/1. In a production kernel without CONFIG_PROVE_LOCKING / CONFIG_LOCKDEP:
    • A child socket new_smc is only enqueued onto lsmc->accept_q in smc_listen_out() after acquiring and immediately releasing &lsmc->sk.
    • Once enqueued in accept_q, smc_listen_work for that socket never attempts to re-acquire &lsmc->sk.
    • Thus, when cancel_work_sync(&new_smc->smc_listen_work) is executed while holding &lsmc->sk, the work item being waited on is already past its lock acquisition (or already terminated) and will not attempt to acquire &lsmc->sk.
    • Consequently, no actual runtime deadlock, hang, crash, or resource leak occurs in production.
▶ ▼ ✨ AI Jobs (11)
ID Workflow Result Correct Bug Created Started Finished Revision
f81e4394 assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ❌ FuzzingArtifact: ❌ MemoryCorruption: ❌ NetworkNeedsSetup: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in smc_release 2026/10/27 03:44 2026/10/27 03:44 2026/10/27 04:12 168cb7a2
ad8c8183 assessment-security 💥 possible deadlock in smc_release 2026/09/26 07:32 2026/09/26 07:32 2026/09/26 07:45 a3c7249d
abd76b75 assessment-security 💥 possible deadlock in smc_release 2026/08/27 02:45 2026/08/27 02:45 2026/08/27 02:55 a2b77b9e
099d19d6 assessment-security 💥 possible deadlock in smc_release 2026/07/27 01:27 2026/07/27 01:27 2026/07/27 01:47 492bab15
ec5e42b9 assessment-security 💥 possible deadlock in smc_release 2026/06/27 01:14 2026/06/27 01:14 2026/06/27 01:39 7ff32d8b
8706df33 assessment-security 💥 possible deadlock in smc_release 2026/06/10 05:11 2026/06/10 05:11 2026/06/10 05:31 34dab4be
3888f937 assessment-security 💥 possible deadlock in smc_release 2026/06/04 08:19 2026/06/04 08:19 2026/06/04 08:33 62fe1528
2a9bf465 assessment-security 💥 possible deadlock in smc_release 2026/06/02 06:25 2026/06/02 06:25 2026/06/02 06:52 1095583b
dcbfaebe patching 💥 possible deadlock in smc_release 2026/05/27 21:29 2026/05/29 17:30 2026/05/29 18:00 6b4a8443
529a6167 assessment-security 💥 possible deadlock in smc_release 2026/05/22 23:48 2026/05/22 23:48 2026/05/23 00:01 df8ac09c
dcf621ed patching 💥 possible deadlock in smc_release 2026/01/29 13:59 2026/01/29 14:02 2026/01/29 14:12 b83e8d3f
▶ ▼ Discussions (11)
Title Replies (including bot) Last reply
[syzbot] Monthly smc report (Nov 2025) 0 (1) 2025/11/03 13:10
[syzbot] Monthly smc report (Sep 2025) 0 (1) 2025/09/18 20:44
[syzbot] Monthly smc report (Aug 2025) 0 (1) 2025/08/18 13:25
[syzbot] Monthly smc report (Jun 2025) 0 (1) 2025/06/16 12:34
[syzbot] Monthly smc report (May 2025) 0 (1) 2025/05/16 10:17
[syzbot] Monthly smc report (Apr 2025) 0 (1) 2025/04/15 10:40
[syzbot] Monthly s390 report (Mar 2025) 0 (1) 2025/03/08 22:17
[syzbot] Monthly s390 report (Feb 2025) 0 (1) 2025/02/05 12:43
[syzbot] Monthly s390 report (Jan 2025) 0 (1) 2025/01/06 10:01
[syzbot] Monthly s390 report (Dec 2024) 0 (1) 2024/12/05 09:07
[syzbot] [net?] [s390?] possible deadlock in smc_release 2 (6) 2024/09/07 16:57
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in smc_release (2) 4 3 12d 162d 0/2 upstream: reported on 2026/05/22 12:09
linux-6.6 possible deadlock in smc_release 4 1 346d 346d 0/2 auto-obsoleted due to no activity on 2026/02/27 23:52
linux-5.15 possible deadlock in smc_release missing-backport origin:lts-only 4 syz, C error 2327 30m 768d 0/3 upstream: reported C repro on 2024/09/24 05:56
linux-6.1 possible deadlock in smc_release origin:upstream missing-backport 4 syz, C 4196 39m 1006d 0/3 upstream: reported C repro on 2024/01/29 16:17
▶ ▼ Last patch testing requests (12)
Created Duration User Patch Repo Result
2025/08/27 13:35 18m retest repro upstream report log
2025/08/27 13:35 14m retest repro upstream report log
2025/01/31 04:29 24m retest repro upstream report log
2024/12/14 14:34 31m retest repro upstream report log
2024/10/17 10:28 23m retest repro upstream report log
2024/08/22 14:03 29m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci no crash log
2024/07/10 03:16 1h55m aha310510@gmail.com patch upstream report log
2024/07/09 03:46 26m aha310510@gmail.com upstream report log
2024/06/10 22:40 24m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2024/06/10 22:40 24m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci no crash log
2024/06/10 22:40 24m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci no crash log
2024/05/27 21:49 21m retest repro upstream no crash log
▶ ▼ Fix bisection attempts (2)
Created Duration User Patch Repo Result
2024/09/07 10:39 6h16m bisect fix net-next OK (1) job log
marked invalid by nogikh@google.com
2024/08/08 08:43 1h38m bisect fix upstream OK (0) job log log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz-executor171/5612 is trying to acquire lock:
ffff888042e2f7b8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
ffff888042e2f7b8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
ffff888042e2f7b8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: start_flush_work kernel/workqueue.c:4354 [inline]
ffff888042e2f7b8 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}, at: __flush_work+0x101/0xd70 kernel/workqueue.c:4412

but task is already holding lock:
ffff888035d31298 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x22f/0x580 net/smc/af_smc.c:-1

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+0x41/0x130 net/core/sock.c:3865
       smc_listen_out+0xd4/0x3d0 net/smc/af_smc.c:1934
       smc_listen_work+0x81d/0x1410 net/smc/af_smc.c:-1
       process_one_work kernel/workqueue.c:3396 [inline]
       process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
       kthread+0x38b/0x470 kernel/kthread.c:436
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 ((work_completion)(&new_smc->smc_listen_work)){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3209 [inline]
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
       touch_work_lockdep_map kernel/workqueue.c:4126 [inline]
       start_flush_work kernel/workqueue.c:4380 [inline]
       __flush_work+0x6c5/0xd70 kernel/workqueue.c:4412
       __cancel_work_sync+0xbf/0x110 kernel/workqueue.c:4568
       smc_clcsock_release+0x60/0xf0 net/smc/smc_close.c:29
       __smc_release+0x662/0x7d0 net/smc/af_smc.c:318
       smc_close_non_accepted+0xd5/0x1f0 net/smc/af_smc.c:1866
       smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
       smc_close_active+0xb59/0xf50 net/smc/smc_close.c:225
       __smc_release+0x9e/0x7d0 net/smc/af_smc.c:294
       smc_release+0x2cd/0x580 net/smc/af_smc.c:361
       __sock_release+0xa0/0x1f0 net/socket.c:735
       sock_close+0x1c/0x30 net/socket.c:1526
       __fput+0x41f/0xa80 fs/file_table.c:512
       fput_close_sync+0x11f/0x240 fs/file_table.c:618
       filp_close_sync+0x6e/0xa0 fs/open.c:1573
       __range_close fs/file.c:919 [inline]
       __do_sys_close_range fs/file.c:1003 [inline]
       __se_sys_close_range+0xa7d/0xf00 fs/file.c:954
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

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 ***

locks held by syz-executor171/5612: 3, last CPU#0:
 #0: ffff888046839038 (&sb->s_type->i_mutex_key#12){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #0: ffff888046839038 (&sb->s_type->i_mutex_key#12){+.+.}-{4:4}, at: __sock_release+0x7a/0x1f0 net/socket.c:734
 #1: ffff888035d31298 (sk_lock-AF_SMC/1){+.+.}-{0:0}, at: smc_release+0x22f/0x580 net/smc/af_smc.c:-1
 #2: ffffffff8f3c3d80 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #2: ffffffff8f3c3d80 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #2: ffffffff8f3c3d80 (rcu_read_lock){....}-{1:3}, at: start_flush_work kernel/workqueue.c:4354 [inline]
 #2: ffffffff8f3c3d80 (rcu_read_lock){....}-{1:3}, at: __flush_work+0x101/0xd70 kernel/workqueue.c:4412

stack backtrace:
CPU: 0 UID: 0 PID: 5612 Comm: syz-executor171 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
 check_prev_add kernel/locking/lockdep.c:3209 [inline]
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 touch_work_lockdep_map kernel/workqueue.c:4126 [inline]
 start_flush_work kernel/workqueue.c:4380 [inline]
 __flush_work+0x6c5/0xd70 kernel/workqueue.c:4412
 __cancel_work_sync+0xbf/0x110 kernel/workqueue.c:4568
 smc_clcsock_release+0x60/0xf0 net/smc/smc_close.c:29
 __smc_release+0x662/0x7d0 net/smc/af_smc.c:318
 smc_close_non_accepted+0xd5/0x1f0 net/smc/af_smc.c:1866
 smc_close_cleanup_listen net/smc/smc_close.c:45 [inline]
 smc_close_active+0xb59/0xf50 net/smc/smc_close.c:225
 __smc_release+0x9e/0x7d0 net/smc/af_smc.c:294
 smc_release+0x2cd/0x580 net/smc/af_smc.c:361
 __sock_release+0xa0/0x1f0 net/socket.c:735
 sock_close+0x1c/0x30 net/socket.c:1526
 __fput+0x41f/0xa80 fs/file_table.c:512
 fput_close_sync+0x11f/0x240 fs/file_table.c:618
 filp_close_sync+0x6e/0xa0 fs/open.c:1573
 __range_close fs/file.c:919 [inline]
 __do_sys_close_range fs/file.c:1003 [inline]
 __se_sys_close_range+0xa7d/0xf00 fs/file.c:954
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9ae652cdc9
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 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 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd19324f78 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9ae652cdc9
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000000000003
RBP: 000000000001923e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd19324fac
R13: 431bde82d7b634db R14: 00007ffd19324fc0 R15: 0000000000000002
 </TASK>

Crashes (1540):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/21 03:40 upstream f47d223627f8 df8746fb .config strace log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in smc_release
2024/01/30 05:21 upstream 41bccc98fb79 991a98f4 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/17 08:11 upstream 70dd4ee72eb2 432c0077 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/08/16 04:41 net 24ef02f934ee 746171ee .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/07/29 01:22 net-next b515dc54795e 19622d9d .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/13 17:29 linux-next 4eb2586bd40d 7321cd29 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in smc_release
2026/10/31 04:18 upstream d89e1d186ec9 0ec395f8 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/07/28 11:05 upstream 62cc90241548 45ae1df4 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in smc_release
2026/06/30 11:13 upstream dc59e4fea9d8 fff8d0a0 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in smc_release
2026/06/30 05:53 upstream dc59e4fea9d8 fff8d0a0 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in smc_release
2024/10/26 22:26 upstream 850925a8133c 65e8686b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in smc_release
2026/10/08 15:12 upstream 7b63ef2d55f2 4f6a9fcf .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/09/16 09:26 upstream 50d05c7c76c9 12a0a44a .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/08/19 17:26 upstream bd5f485f3f02 1e72964b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/14 18:52 upstream 4056b3c9d3c9 1a71827b .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/08 14:21 upstream 0c2669a9f4a1 9d4697fa .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/09/29 21:45 upstream 6f8319e3e9a4 328436b3 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in smc_release
2026/09/27 09:49 upstream fd179f8a05be a3c7249d .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in smc_release
2026/09/01 07:50 upstream bf1079577a11 316d9396 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/08/07 04:16 upstream fcaeecb8b0cd c38879ea .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/07/09 07:03 upstream 0e35b9b6ec0f b9f1ceaa .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/06/13 17:37 upstream 062871f1371b 4f06757f .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/06/11 12:00 upstream 9716c086c8e8 d93a6ab6 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2025/08/08 21:48 upstream bec077162bd0 56444e07 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2025/08/08 15:05 upstream bec077162bd0 56444e07 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/17 17:23 upstream 58161ead29e5 432c0077 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/10/09 11:05 upstream 6c377d19d4a5 b2734a59 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/08/16 05:19 upstream 3eb40771c00a 746171ee .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/10/22 07:49 net abeacca61eea 4ba27f85 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/09/22 09:30 net 12fec40907fa e12281bd .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/09/19 13:53 net 6c096bb08de9 853b104b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/07/28 12:41 net 9c88929cc18c 45ae1df4 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/06/17 10:47 net 406e8a651a7b 62cc6db3 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/17 10:21 net-next 95a5c641fc7b 432c0077 .config strace log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/09/27 15:20 net-next 014d795c7383 a3c7249d .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/09/18 10:15 net-next 26ee8cd69d46 8d7d05f1 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/07/01 01:16 net-next cef9d6804030 00e8b0fd .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/06/09 02:37 net-next d337bc6b2707 656e94c6 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/06/06 14:28 net-next 2eb9a81a7f73 cc095639 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/03 20:02 linux-next f0406245cb98 57bbd979 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in smc_release
2026/10/03 18:37 linux-next f0406245cb98 57bbd979 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in smc_release
2026/08/24 05:04 linux-next 903c1cf6dff9 1e72964b .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in smc_release
2026/06/17 12:20 linux-next ec039126b7fa 62cc6db3 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in smc_release
2026/09/08 09:27 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 5445d6419962 680aa3e1 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2026/08/03 12:55 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7235a3e71949 e611ffe1 .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2024/01/30 02:42 upstream 41bccc98fb79 991a98f4 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2024/01/27 04:09 upstream 168174d78157 cc4a4020 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2024/01/27 02:42 net fcf67d82b8b8 cc4a4020 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2024/01/27 03:15 net-next 5f76499fb541 cc4a4020 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2024/01/30 00:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 991a98f4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2024/01/30 00:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 991a98f4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2024/01/27 03:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca cc4a4020 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2026/10/31 01:58 upstream d89e1d186ec9 0ec395f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in smc_release
2026/10/30 21:17 upstream d89e1d186ec9 0ec395f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/30 18:51 upstream d89e1d186ec9 0ec395f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in smc_release
2026/10/30 04:55 upstream 4dd16e31135e b498adee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/29 23:19 upstream 4dd16e31135e b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in smc_release
2026/10/29 12:12 upstream c339f4010dea b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/28 11:47 upstream 65ba8f34ec88 858db2ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in smc_release
2026/10/28 07:24 upstream 62c457528529 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/28 01:20 upstream d135ab453a74 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in smc_release
2026/10/27 09:21 upstream d135ab453a74 168cb7a2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in smc_release
2026/10/27 03:00 upstream 6b4b543fa187 168cb7a2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in smc_release
2026/10/27 00:06 upstream 6b4b543fa187 168cb7a2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in smc_release
2026/10/26 13:00 upstream 12392d40a3be 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/26 00:40 upstream 21a7f44fd076 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in smc_release
2026/10/25 15:54 upstream 21a7f44fd076 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/24 16:13 upstream 4da9dedf3fc5 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in smc_release
2026/10/23 00:49 upstream 2a08195e4db5 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/22 23:24 upstream 2a08195e4db5 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/22 11:54 upstream 4403278e4ea2 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in smc_release
2026/10/22 10:36 upstream 9ba46df34488 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in smc_release
2026/10/22 05:21 upstream 9ba46df34488 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in smc_release
2026/08/13 01:04 upstream 3d6d817622b0 359b2492 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in smc_release
2026/10/29 03:10 upstream c339f4010dea b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/26 04:37 upstream 12392d40a3be 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/25 06:23 upstream 5b0764a53235 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/23 06:59 upstream 2a08195e4db5 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/21 08:46 upstream 9e947d96915a 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/20 23:57 upstream f47d223627f8 df8746fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in smc_release
2026/10/31 08:17 upstream abf8c33470f7 2041d3f8 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in smc_release
2026/10/30 13:21 upstream d89e1d186ec9 0ec395f8 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/28 02:50 upstream 62c457528529 96923c60 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in smc_release
2026/10/27 23:39 upstream 62c457528529 96923c60 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/27 19:51 upstream 62c457528529 96923c60 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/26 22:52 upstream 6b4b543fa187 168cb7a2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/22 14:53 upstream 7be4bc52fd9e 3875c4e4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in smc_release
2026/10/28 08:57 upstream 65ba8f34ec88 96923c60 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/10/26 10:50 upstream 6b4b543fa187 168cb7a2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/10/24 23:54 upstream 5b0764a53235 1d9ca40b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/10/23 13:33 upstream 734bef548a96 1d9ca40b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in smc_release
2026/11/01 04:36 net cb284914e749 25a0ae84 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/30 09:08 net 5838f10563d5 b498adee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/28 05:05 net f75062536e2d 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/27 21:02 net f75062536e2d 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/27 18:48 net f75062536e2d 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/27 15:57 net f75062536e2d 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/26 09:44 net 6430fb7f1cc4 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/24 12:30 net 7076f684d513 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/21 19:19 net c0703534b223 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/21 09:50 net c0703534b223 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in smc_release
2026/10/30 22:49 net-next 4dd16e31135e 0ec395f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/29 06:18 net-next 734bef548a96 b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/28 22:58 net-next 734bef548a96 858db2ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/28 16:43 net-next 734bef548a96 858db2ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/27 14:29 net-next 734bef548a96 96923c60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/24 19:25 net-next 734bef548a96 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2026/10/21 10:52 net-next 599d0e97610f 61c200c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in smc_release
2024/03/04 04:16 net-next 4b2765ae410a 25905f5d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-net-next-test-gce possible deadlock in smc_release
2026/10/26 07:19 linux-next 20a33c6b6cbe 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in smc_release
2026/10/24 22:17 linux-next 20a33c6b6cbe 1d9ca40b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in smc_release
2026/10/22 09:04 linux-next 9a482184d910 4ba27f85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in smc_release
2026/10/21 05:10 linux-next 8f7df005a756 df8746fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in smc_release
2026/10/29 20:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad b1d00f76 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2026/10/28 19:28 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 7a19f0cc94ad 858db2ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in smc_release
2025/09/09 04:41 git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git for-next 8f5ae30d69d7 d291dd2d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-riscv64 possible deadlock in smc_release
* Struck through repros no longer work on HEAD.