[v6.6] WARNING in nilfs_palloc_commit_alloc_entry

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 258cf62a6dfd Linux 6.6.137
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=114ed748580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c5b35c4db8465904
dashboard link: https://syzkaller.appspot.com/bug?extid=b5942f50041c607beb24
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e6576c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10dd396a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8abd93876bdd/disk-258cf62a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/721d0cc7467a/vmlinux-258cf62a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7f2dfd911e3d/bzImage-258cf62a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/06ca0cfdcd13/mount_0.gz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5954 at fs/buffer.c:1188 mark_buffer_dirty+0x2bb/0x4c0 fs/buffer.c:1188
Modules linked in:

CPU: 0 PID: 5954 Comm: syz.0.22 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:mark_buffer_dirty+0x2bb/0x4c0 fs/buffer.c:1188
Code: 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 9f 9a fc ff e8 ba b6 88 ff 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 ea 08 e8 ff e8 a5 b6 88 ff <0f> 0b e9 84 fd ff ff e8 99 b6 88 ff 0f 0b e9 b0 fd ff ff e8 8d b6
RSP: 0018:ffffc90003337330 EFLAGS: 00010293
RAX: ffffffff81fe6b5b RBX: ffff88805f724570 RCX: ffff888029209e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: 1ffff1100f692101 R08: ffff88805f724577 R09: 1ffff1100bee48ae
R10: dffffc0000000000 R11: ffffed100bee48af R12: dffffc0000000000
R13: 1ffff1100f6921e8 R14: ffff88807b490f48 R15: ffff888076a31af8
FS: 00007f57dcae16c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000004e000 CR3: 000000006bde4000 CR4: 00000000003506f0
Call Trace:
<TASK>
nilfs_palloc_commit_alloc_entry+0x6a/0x150 fs/nilfs2/alloc.c:597
nilfs_dat_commit_alloc+0x1b7/0x2d0 fs/nilfs2/dat.c:102
nilfs_bmap_commit_alloc_ptr fs/nilfs2/bmap.h:194 [inline]
nilfs_btree_commit_insert fs/nilfs2/btree.c:1226 [inline]
nilfs_btree_insert+0x13f6/0x1b30 fs/nilfs2/btree.c:1256
nilfs_bmap_do_insert fs/nilfs2/bmap.c:129 [inline]
nilfs_bmap_insert+0x242/0x3f0 fs/nilfs2/bmap.c:155
nilfs_get_block+0x3fa/0x930 fs/nilfs2/inode.c:101
__block_write_begin_int+0x57f/0x1af0 fs/buffer.c:2124
__block_write_begin fs/buffer.c:2173 [inline]
block_write_begin+0x9a/0x1e0 fs/buffer.c:2234
nilfs_write_begin+0xa3/0x110 fs/nilfs2/inode.c:261
generic_perform_write+0x2fe/0x5c0 mm/filemap.c:4036
__generic_file_write_iter+0x1ac/0x230 mm/filemap.c:4128
generic_file_write_iter+0xaf/0x2e0 mm/filemap.c:4157
do_iter_readv_writev fs/read_write.c:-1 [inline]
do_iter_write+0x738/0xc30 fs/read_write.c:860
vfs_writev fs/read_write.c:933 [inline]
do_pwritev+0x241/0x3a0 fs/read_write.c:1030
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f57dbb9cdd9
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:00007f57dcae1028 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007f57dbe15fa0 RCX: 00007f57dbb9cdd9
RDX: 0000000000000001 RSI: 0000200000000240 RDI: 0000000000000004
RBP: 00007f57dbc32d69 R08: 0000000000000000 R09: 0000000000000003
R10: 0000000000002000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f57dbe16038 R14: 00007f57dbe15fa0 R15: 00007fff79cd7808
</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 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