possible deadlock in __kernfs_remove (3)

Status: upstream: reported C repro on 2026/02/26 06:07
Subsystems: input
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+1075f6dc93f398c1857e@syzkaller.appspotmail.com
First crash: 241d, last: 5h23m
Cause bisection: failed (error log, bisect log)
  
▶ ▼ ✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
e032206d patching 💥 possible deadlock in __kernfs_remove (3) 2026/09/02 20:17 2026/09/02 20:37 2026/09/02 20:37 9941e97d
d048112f assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ✅ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in __kernfs_remove (3) 2026/05/31 02:34 2026/05/31 02:34 2026/05/31 03:38 6b4a8443
7897c675 assessment-security 💥 possible deadlock in __kernfs_remove (3) 2026/05/14 13:41 2026/05/14 13:41 2026/05/14 13:42 6ccb967e
▶ ▼ Discussions (7)
Title Replies (including bot) Last reply
[PATCH v3] Input: serio - don't sleep on serio_mutex from drvctl_store() 1 (1) 2026/09/24 04:32
[PATCH] Input: serio - don't sleep on serio_mutex from drvctl_store() 3 (3) 2026/09/24 04:09
[PATCH v2] Input: serio - don't sleep on serio_mutex from drvctl_store() 1 (1) 2026/09/24 04:04
[syzbot] [kernfs?] possible deadlock in __kernfs_remove (3) 0 (3) 2026/08/29 21:22
[syzbot] Monthly input report (Aug 2026) 0 (1) 2026/08/24 04:32
[syzbot] Monthly kernfs report (Aug 2026) 0 (1) 2026/08/02 00:00
[syzbot] Monthly kernfs report (Jul 2026) 0 (1) 2026/07/01 12:32
▶ ▼ Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 possible deadlock in __kernfs_remove 4 5 3h28m 56d 0/2 upstream: reported on 2026/08/25 23:30
linux-6.1 possible deadlock in __kernfs_remove 4 syz, C 15 22h34m 61d 0/3 upstream: reported C repro on 2026/08/21 21:40
upstream possible deadlock in __kernfs_remove kernfs 4 syz, C 438 806d 849d 28/29 fixed on 2024/10/03 15:25
upstream possible deadlock in __kernfs_remove (2) kernfs 4 syz, C 4976 544d 712d 0/29 auto-obsoleted due to no activity on 2025/07/04 15:33
▶ ▼ Cause bisection attempts (3)
Created Duration User Patch Repo Result
2026/10/13 15:28 13m bisect upstream error job log
2026/09/20 17:08 0m bisect upstream error
2026/09/02 04:57 0m bisect upstream error

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.20/6033 is trying to acquire lock:
ffff88802963df08 (kn->active#66){++++}-{0:0}, at: __kernfs_remove+0x34c/0xb80 fs/kernfs/dir.c:1579

but task is already holding lock:
ffffffff904e2860 (serio_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
ffffffff904e2860 (serio_mutex){+.+.}-{4:4}, at: serio_unregister_port+0x1b/0x40 drivers/input/serio/serio.c:677

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (serio_mutex){+.+.}-{4:4}:
       lock_acquire kernel/locking/lockdep.c:5908 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5865
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x1a4/0x1bd0 kernel/locking/mutex.c:821
       class_mutex_intr_constructor include/linux/mutex.h:255 [inline]
       drvctl_store+0x3c/0x350 drivers/input/serio/serio.c:360
       dev_attr_store+0x58/0x80 drivers/base/core.c:2509
       sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145
       kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x6af/0x1050 fs/read_write.c:687
       ksys_write+0x12a/0x250 fs/read_write.c:739
       do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:79 [inline]
       __do_fast_syscall_32+0x13a/0x8b0 arch/x86/entry/syscall_32.c:291
       do_fast_syscall_32+0x32/0x70 arch/x86/entry/syscall_32.c:316
       entry_SYSENTER_compat_after_hwframe+0x84/0x8e

-> #0 (kn->active#66){++++}-{0:0}:
       check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
       check_prevs_add kernel/locking/lockdep.c:3300 [inline]
       validate_chain kernel/locking/lockdep.c:3924 [inline]
       __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5254
       lock_acquire kernel/locking/lockdep.c:5908 [inline]
       lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5865
       kernfs_drain+0x4f0/0x600 fs/kernfs/dir.c:532
       __kernfs_remove+0x34c/0xb80 fs/kernfs/dir.c:1579
       kernfs_remove_by_name_ns+0x7c/0x120 fs/kernfs/dir.c:1797
       kernfs_remove_by_name include/linux/kernfs.h:644 [inline]
       remove_files+0x96/0x1c0 fs/sysfs/group.c:28
       sysfs_remove_group+0x8b/0x1b0 fs/sysfs/group.c:328
       sysfs_remove_groups fs/sysfs/group.c:352 [inline]
       sysfs_remove_groups+0x60/0xb0 fs/sysfs/group.c:344
       device_remove_groups drivers/base/core.c:2918 [inline]
       device_remove_attrs+0x192/0x290 drivers/base/core.c:3048
       device_del+0x36e/0x9b0 drivers/base/core.c:3964
       serio_destroy_port+0x47f/0x590 drivers/input/serio/serio.c:543
       serio_unregister_port+0x2b/0x40 drivers/input/serio/serio.c:680
       userio_char_release+0x91/0xe0 drivers/input/serio/userio.c:105
       __fput+0x3ff/0xb50 fs/file_table.c:512
       task_work_run+0x150/0x240 kernel/task_work.c:233
       resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
       __exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
       exit_to_user_mode_loop+0x1d8/0x700 kernel/entry/common.c:101
       __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
       syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
       syscall_exit_to_user_mode include/linux/entry-common.h:336 [inline]
       __do_fast_syscall_32+0x59f/0x8b0 arch/x86/entry/syscall_32.c:294
       do_fast_syscall_32+0x32/0x70 arch/x86/entry/syscall_32.c:316
       entry_SYSENTER_compat_after_hwframe+0x84/0x8e

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(serio_mutex);
                               lock(kn->active#66);
                               lock(serio_mutex);
  lock(kn->active#66);

 *** DEADLOCK ***

locks held by syz.3.20/6033: 1, last CPU#0:
 #0: ffffffff904e2860 (serio_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #0: ffffffff904e2860 (serio_mutex){+.+.}-{4:4}, at: serio_unregister_port+0x1b/0x40 drivers/input/serio/serio.c:677

stack backtrace:
CPU: 0 UID: 0 PID: 6033 Comm: syz.3.20 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 print_circular_bug.cold+0x178/0x1be kernel/locking/lockdep.c:2059
 check_noncircular+0x146/0x160 kernel/locking/lockdep.c:2191
 check_prev_add+0xeb/0xe60 kernel/locking/lockdep.c:3181
 check_prevs_add kernel/locking/lockdep.c:3300 [inline]
 validate_chain kernel/locking/lockdep.c:3924 [inline]
 __lock_acquire+0x1492/0x1ec0 kernel/locking/lockdep.c:5254
 lock_acquire kernel/locking/lockdep.c:5908 [inline]
 lock_acquire+0x1d1/0x380 kernel/locking/lockdep.c:5865
 kernfs_drain+0x4f0/0x600 fs/kernfs/dir.c:532
 __kernfs_remove+0x34c/0xb80 fs/kernfs/dir.c:1579
 kernfs_remove_by_name_ns+0x7c/0x120 fs/kernfs/dir.c:1797
 kernfs_remove_by_name include/linux/kernfs.h:644 [inline]
 remove_files+0x96/0x1c0 fs/sysfs/group.c:28
 sysfs_remove_group+0x8b/0x1b0 fs/sysfs/group.c:328
 sysfs_remove_groups fs/sysfs/group.c:352 [inline]
 sysfs_remove_groups+0x60/0xb0 fs/sysfs/group.c:344
 device_remove_groups drivers/base/core.c:2918 [inline]
 device_remove_attrs+0x192/0x290 drivers/base/core.c:3048
 device_del+0x36e/0x9b0 drivers/base/core.c:3964
 serio_destroy_port+0x47f/0x590 drivers/input/serio/serio.c:543
 serio_unregister_port+0x2b/0x40 drivers/input/serio/serio.c:680
 userio_char_release+0x91/0xe0 drivers/input/serio/userio.c:105
 __fput+0x3ff/0xb50 fs/file_table.c:512
 task_work_run+0x150/0x240 kernel/task_work.c:233
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 __exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
 exit_to_user_mode_loop+0x1d8/0x700 kernel/entry/common.c:101
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:336 [inline]
 __do_fast_syscall_32+0x59f/0x8b0 arch/x86/entry/syscall_32.c:294
 do_fast_syscall_32+0x32/0x70 arch/x86/entry/syscall_32.c:316
 entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf70aefec
Code: Unable to access opcode bytes at 0xf70aefc2.
RSP: 002b:00000000ff87a3cc EFLAGS: 00000202 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 000000000000001e
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (330):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/06 01:40 upstream 4d7d9486c04d 4f7b22a0 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/08/29 21:22 upstream cf72cbb39da8 2f52988a .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/09/03 17:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci cee9395acd80 6a988719 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __kernfs_remove
2026/08/26 00:47 upstream 66498c75b4f8 614e416a .config console log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __kernfs_remove
2026/08/23 03:22 upstream 66fb95a52111 1e72964b .config strace log report syz / log [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __kernfs_remove
2026/08/28 06:30 upstream 18fbf5151d2c e2fa417d .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/11 05:38 upstream a5ebb76233b7 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __kernfs_remove
2026/10/10 07:57 upstream 3857c2fe5449 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __kernfs_remove
2026/10/09 07:04 upstream 6c377d19d4a5 b2734a59 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __kernfs_remove
2026/10/07 16:14 upstream 602042bf29f6 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __kernfs_remove
2026/10/04 21:58 upstream 6addb4f38557 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in __kernfs_remove
2026/09/05 23:15 upstream 0d9ff90a5422 4f7b22a0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in __kernfs_remove
2026/09/03 15:10 upstream 940de590b839 6a988719 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __kernfs_remove
2026/04/23 06:45 upstream 2a4c0c11c019 b10da5ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in __kernfs_remove
2026/10/21 17:25 upstream a804c5742bff 42e06812 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/21 15:56 upstream a804c5742bff 42e06812 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/21 06:26 upstream 4cbdd58dfa7a 61c200c7 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/21 01:28 upstream 4cbdd58dfa7a 61c200c7 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/20 12:19 upstream f47d223627f8 df8746fb .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/19 19:07 upstream c03c1a14507d 440f8011 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/18 23:43 upstream a0ff06b3a7bd 432c0077 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in __kernfs_remove
2026/10/17 03:45 upstream 70dd4ee72eb2 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/16 11:00 upstream 2f2f7eeef8b0 b1757810 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/16 02:15 upstream 045958acaa75 3f2522c6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/15 19:07 upstream 045958acaa75 3f2522c6 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/15 05:04 upstream 0fcb05b72344 8fb0ae89 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in __kernfs_remove
2026/10/14 17:40 upstream 4056b3c9d3c9 1a71827b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/14 02:17 upstream ca3e345926b0 7321cd29 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/13 23:33 upstream 24a19b953e2a 7321cd29 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/13 09:51 upstream 24a19b953e2a 5a1eeac4 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/13 02:08 upstream 24a19b953e2a 745a967f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root possible deadlock in __kernfs_remove
2026/10/11 14:06 upstream a5ebb76233b7 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/11 10:33 upstream a5ebb76233b7 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/11 01:56 upstream a5ebb76233b7 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/11 01:18 upstream a5ebb76233b7 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 20:35 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 18:49 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 14:27 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 13:26 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 12:24 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 10:28 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/10 06:53 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/09 20:25 upstream af32da41b032 549ef7e3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/09 14:30 upstream af32da41b032 549ef7e3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/09 02:28 upstream 6c377d19d4a5 b2734a59 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/09 02:28 upstream 6c377d19d4a5 b2734a59 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in __kernfs_remove
2026/10/20 14:45 upstream f47d223627f8 df8746fb .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/20 13:33 upstream f47d223627f8 df8746fb .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/18 20:16 upstream a0ff06b3a7bd 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/18 17:31 upstream 32c52ec87d62 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/17 13:48 upstream 58161ead29e5 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/16 23:55 upstream 70dd4ee72eb2 432c0077 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/16 15:46 upstream 2f2f7eeef8b0 b1757810 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/16 12:51 upstream 2f2f7eeef8b0 b1757810 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/16 11:00 upstream 2f2f7eeef8b0 b1757810 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/15 11:41 upstream 0fcb05b72344 8fb0ae89 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/15 09:09 upstream 0fcb05b72344 8fb0ae89 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/12 23:58 upstream 24a19b953e2a 745a967f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/10 02:59 upstream 3857c2fe5449 4f92358f .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/09 15:57 upstream af32da41b032 549ef7e3 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/09 00:06 upstream 0c2669a9f4a1 9d4697fa .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in __kernfs_remove
2026/10/12 03:14 net af32da41b032 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __kernfs_remove
2026/02/27 19:35 net be11a537224d 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __kernfs_remove
2026/02/22 05:56 net d4f687fbbce4 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in __kernfs_remove
2026/10/08 07:09 net-next 6a8b493c68e0 6520ecdb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in __kernfs_remove
2026/10/05 19:14 linux-next bf1ee2bd5c2d 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce possible deadlock in __kernfs_remove
2026/09/13 13:42 linux-next a9d7ced84989 70a60e12 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in __kernfs_remove
2026/09/27 07:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e8e60d3ddd25 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __kernfs_remove
* Struck through repros no longer work on HEAD.