[syzbot] [fs?] WARNING in V1_minix_truncate (2)

[syzbot <syzbot+e353ad4408c4f9fac965@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    b88c841d1164 Merge tag 'input-for-v7.3-rc6' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1043540d580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7d1b274ca9837366
dashboard link: https://syzkaller.appspot.com/bug?extid=e353ad4408c4f9fac965
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1280a9c9580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-b88c841d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c64cd81f2bae/vmlinux-b88c841d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/605b0408da7b/bzImage-b88c841d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/bf4cfcb2c7e6/mount_13.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e353ad4408c4f9fac965@syzkaller.appspotmail.com

IO error syncing minix inode [loop0:00000008]
------------[ cut here ]------------
!buffer_uptodate(bh)
WARNING: fs/buffer.c:991 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:991, CPU#0: syz.0.182/5880
Modules linked in:
CPU: 0 UID: 0 PID: 5880 Comm: syz.0.182 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
RIP: 0010:mark_buffer_dirty+0x299/0x410 fs/buffer.c:991
Code: 4c 89 f7 e8 d9 d5 d7 ff 49 8b 3e be 40 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 34 44 fb ff e8 8f 56 65 ff eb 8c e8 88 56 65 ff 90 <0f> 0b 90 e9 a5 fd ff ff e8 7a 56 65 ff 90 0f 0b 90 e9 cf fd ff ff
RSP: 0018:ffffc90004a979f0 EFLAGS: 00010293
RAX: ffffffff8262ca98 RBX: ffff8880459b49a0 RCX: ffff888034650000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90004a97b01 R08: ffff8880459b49a7 R09: 1ffff11008b36934
R10: dffffc0000000000 R11: ffffed1008b36935 R12: ffff88800bf46596
R13: ffff88800bf46620 R14: ffff88800bf46588 R15: 0000000000000017
FS:  00007ff0885f46c0(0000) GS:ffff88808b0b4000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f24c7d6a000 CR3: 000000001d368000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 free_data fs/minix/itree_common.c:272 [inline]
 truncate fs/minix/itree_common.c:321 [inline]
 V1_minix_truncate+0x310/0x10c0 fs/minix/itree_v1.c:61
 minix_truncate fs/minix/inode.c:750 [inline]
 minix_evict_inode+0x1c9/0x260 fs/minix/inode.c:52
 evict+0x624/0xb50 fs/inode.c:822
 minix_mkdir+0xdc/0x120 fs/minix/namei.c:136
 vfs_mkdir+0x40c/0x620 fs/namei.c:5439
 filename_mkdirat+0x285/0x510 fs/namei.c:5472
 __do_sys_mkdirat fs/namei.c:5493 [inline]
 __se_sys_mkdirat+0x35/0x150 fs/namei.c:5490
 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:0x7ff08779e1d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff0885f4028 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ff087a25fa0 RCX: 00007ff08779e1d9
RDX: 00000000000001c0 RSI: 0000200000000700 RDI: ffffffffffffff9c
RBP: 00007ff087835888 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff087a26038 R14: 00007ff087a25fa0 R15: 00007fff1b9cc468
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup