WARNING in minix_rmdir (2)

Status: upstream: reported C repro on 2026/10/16 07:32
Subsystems: fs
Labels: prio:high
[Documentation on labels]
Reported-by: syzbot+8420e667af06b1709c00@syzkaller.appspotmail.com
First crash: 4d13h, last: 6h49m
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
92bf0784 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ WARNING in minix_rmdir (2) 2026/10/13 04:34 2026/10/13 04:34 2026/10/13 04:39 745a967f
▶ ▼ Discussions (2)
Title Replies (including bot) Last reply
[PATCH] minix: reject rmdir of a directory with a corrupted link count 1 (1) 2026/10/16 11:58
[syzbot] [fs?] WARNING in minix_rmdir (2) 0 (1) 2026/10/16 07:32
▶ ▼ Similar bugs (6)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 WARNING in minix_rmdir -1 syz, C done 1 372d 372d 3/3 fixed on 2025/11/17 11:56
linux-6.6 WARNING in minix_rmdir origin:lts-only -1 syz, C error 15 95d 292d 0/2 upstream: reported C repro on 2025/12/27 21:41
linux-5.15 WARNING in minix_rmdir -1 1 691d 691d 0/3 auto-obsoleted due to no activity on 2025/03/04 02:00
linux-5.15 WARNING in minix_rmdir (2) origin:upstream -1 syz, C error 9 50d 446d 0/3 upstream: reported C repro on 2025/07/27 03:10
linux-6.1 WARNING in minix_rmdir (2) origin:lts-only -1 syz, C error 4 275d 275d 0/3 upstream: reported C repro on 2026/01/13 22:36
upstream WARNING in minix_rmdir fs -1 syz, C inconclusive 92 332d 646d 29/29 fixed on 2026/01/07 12:29
▶ ▼ Cause bisection attempts (1)
Created Duration User Patch Repo Result
2026/10/16 16:59 bisect upstream running

Sample crash report:
loop0: detected capacity change from 0 to 64
------------[ cut here ]------------
inode->i_nlink == 0
WARNING: fs/inode.c:408 at drop_nlink+0xc5/0x110 fs/inode.c:408, CPU#1: syz-executor191/5598
Modules linked in:
CPU: 1 UID: 0 PID: 5598 Comm: syz-executor191 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
RIP: 0010:drop_nlink+0xc5/0x110 fs/inode.c:408
Code: 50 09 00 00 be 08 00 00 00 e8 57 42 e9 ff f0 48 ff 83 50 09 00 00 5b 41 5c 41 5e 41 5f 5d e9 c2 fb 13 09 cc e8 7c 7a 7c ff 90 <0f> 0b 90 eb 81 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 5b ff ff ff
RSP: 0018:ffffc90004c2fd10 EFLAGS: 00010293
RAX: ffffffff824a5ee4 RBX: ffff888034639398 RCX: ffff8880394c8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff2164730 R12: 1ffff110068c727c
R13: dffffc0000000000 R14: ffff8880346393e0 R15: dffffc0000000000
FS:  000055558d7ec400(0000) GS:ffff888124abb000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdb49f75000 CR3: 000000003c6f4000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 inode_dec_link_count include/linux/fs.h:2269 [inline]
 minix_rmdir+0xfc/0x140 fs/minix/namei.c:183
 vfs_rmdir+0x3e9/0x6b0 fs/namei.c:5544
 filename_rmdir+0x292/0x520 fs/namei.c:5601
 __do_sys_rmdir fs/namei.c:5624 [inline]
 __se_sys_rmdir+0x2e/0x140 fs/namei.c:5621
 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:0x7f656e7f4869
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:00007fffc6075818 EFLAGS: 00000246 ORIG_RAX: 0000000000000054
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f656e7f4869
RDX: 00007fffc60756a0 RSI: 0000000000000000 RDI: 0000200000000040
RBP: 0000000000000001 R08: 0000000000000000 R09: 000055558d7ed560
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffc6075840
R13: 0000000000000002 R14: 431bde82d7b634db R15: 00007f656e85404b
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/16 14:38 upstream 2f2f7eeef8b0 4c840a2f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in minix_rmdir
2026/10/12 12:18 upstream b88c841d1164 4f92358f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in minix_rmdir
2026/10/12 11:18 upstream b88c841d1164 4f92358f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in minix_rmdir
2026/10/12 10:26 upstream b88c841d1164 4f92358f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in minix_rmdir
2026/10/12 09:31 upstream b88c841d1164 4f92358f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in minix_rmdir
2026/10/12 08:47 upstream b88c841d1164 4f92358f .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root WARNING in minix_rmdir
2026/10/12 07:29 upstream b88c841d1164 4f92358f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root WARNING in minix_rmdir
* Struck through repros no longer work on HEAD.