[moderation] [fs?] WARNING in evict (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3aa1dcaa4f6f Revert "wifi: mt76: Disable napi when removin..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=103b0c79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a59830cba91a1981
dashboard link: https://syzkaller.appspot.com/bug?extid=9f4809929f7e4aa2994d
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-3aa1dcaa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9ca8884fc6df/vmlinux-3aa1dcaa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7cee81124451/bzImage-3aa1dcaa.xz

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

Unable to read inode block
------------[ 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/5317
Modules linked in:
CPU: 0 UID: 0 PID: 5317 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 99 fd d8 ff 49 8b 3e be 40 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 04 5e fb ff e8 cf c7 69 ff eb 8c e8 c8 c7 69 ff 90 <0f> 0b 90 e9 a5 fd ff ff e8 ba c7 69 ff 90 0f 0b 90 e9 cf fd ff ff
RSP: 0018:ffffc9000e2978b0 EFLAGS: 00010283
RAX: ffffffff825d49e8 RBX: ffff8880438e9c40 RCX: 0000000000100000
RDX: ffffc9000f7b9000 RSI: 0000000000000e9c RDI: 0000000000000e9d
RBP: ffffc9000e297a01 R08: ffff8880438e9c47 R09: 1ffff1100871d388
R10: dffffc0000000000 R11: ffffed100871d389 R12: ffff8880439230b0
R13: 1ffff92001c52f28 R14: ffffffff82aa3bd0 R15: 0000000000000001
FS: 00007ff50dbd46c0(0000) GS:ffff88808c547000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc9a9871270 CR3: 0000000012bb3000 CR4: 0000000000352ef0
Call Trace:
<TASK>
evict+0x624/0xb50 fs/inode.c:825
add_nondir fs/minix/namei.c:18 [inline]
minix_mknod fs/minix/namei.c:50 [inline]
minix_create+0x88/0xb0 fs/minix/namei.c:69
lookup_open fs/namei.c:4508 [inline]
open_last_lookups fs/namei.c:4608 [inline]
path_openat+0x133a/0x3830 fs/namei.c:4860
do_file_open+0x23e/0x4a0 fs/namei.c:4892
do_sys_openat2+0x115/0x200 fs/open.c:1368
do_sys_open fs/open.c:1374 [inline]
__do_sys_openat fs/open.c:1390 [inline]
__se_sys_openat fs/open.c:1385 [inline]
__x64_sys_openat+0x138/0x170 fs/open.c:1385
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:0x7ff51179e0d9
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:00007ff50dbd3fe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007ff511a26090 RCX: 00007ff51179e0d9
RDX: 000000000000275a RSI: 0000200000000080 RDI: ffffffffffffff9c
RBP: 00007ff511835024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff511a26128 R14: 00007ff511a26090 R15: 00007ffdbc66c378
</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