[moderation] [fs?] WARNING in V1_minix_truncate

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 665159e24674 Merge tag 'probes-fixes-v7.2-rc1' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15c70e1c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c3d59be33cf7e9a
dashboard link: https://syzkaller.appspot.com/bug?extid=4d27b5957299969c64b8
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-665159e2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/79fa1a9752ec/vmlinux-665159e2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/69f865896e1b/bzImage-665159e2.xz

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

loop0: detected capacity change from 0 to 64
Buffer I/O error on dev loop0, logical block 6, async page read
------------[ cut here ]------------
!buffer_uptodate(bh)
WARNING: fs/buffer.c:1093 at mark_buffer_dirty+0x299/0x410 fs/buffer.c:1093, CPU#0: syz.0.0/5322
Modules linked in:
CPU: 0 UID: 0 PID: 5322 Comm: syz.0.0 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:1093
Code: 4c 89 f7 e8 c9 11 d9 ff 49 8b 3e be 40 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 d4 5e fb ff e8 9f f3 69 ff eb 8c e8 98 f3 69 ff 90 <0f> 0b 90 e9 a5 fd ff ff e8 8a f3 69 ff 90 0f 0b 90 e9 cf fd ff ff
RSP: 0018:ffffc9000e99f9f0 EFLAGS: 00010293
RAX: ffffffff825c7e78 RBX: ffff8880441ef8c0 RCX: ffff888038c20000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc9000e99fb01 R08: ffff8880441ef8c7 R09: 1ffff1100883df18
R10: dffffc0000000000 R11: ffffed100883df19 R12: ffff88801fc4b57e
R13: ffff88801fc4b608 R14: ffff88801fc4b570 R15: 0000000000000017
FS: 00007fad2f3ff6c0(0000) GS:ffff88808c815000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcee5ff3720 CR3: 000000001bea0000 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:732 [inline]
minix_evict_inode+0x1c9/0x260 fs/minix/inode.c:50
evict+0x624/0xb50 fs/inode.c:825
minix_mkdir+0xe2/0x120 fs/minix/namei.c:136
vfs_mkdir+0x406/0x620 fs/namei.c:5272
filename_mkdirat+0x285/0x510 fs/namei.c:5305
__do_sys_mkdir fs/namei.c:5332 [inline]
__se_sys_mkdir+0x34/0x150 fs/namei.c:5329
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fad2e59de59
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:00007fad2f3fefe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007fad2e825fa0 RCX: 00007fad2e59de59
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000005900
RBP: 00007fad2e633e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fad2e826038 R14: 00007fad2e825fa0 R15: 00007ffc3fc0b248
</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 syzk...@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 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