[v6.6] WARNING in mark_buffer_dirty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59a2de10b81a Linux 6.6.97
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ff10f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac0b29aca872266f
dashboard link: https://syzkaller.appspot.com/bug?extid=1d3cc35f66cd8ede91bf
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32864b54a55c/disk-59a2de10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b0bbe4ada642/vmlinux-59a2de10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e3fe91e14c2/bzImage-59a2de10.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 13886 at fs/buffer.c:1188 mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Modules linked in:
CPU: 1 PID: 13886 Comm: segctord Not tainted 6.6.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Code: 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 ef ac fc ff e8 ca 95 88 ff 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 fa 57 e8 ff e8 b5 95 88 ff <0f> 0b e9 84 fd ff ff e8 a9 95 88 ff 0f 0b e9 b0 fd ff ff e8 9d 95
RSP: 0018:ffffc90018d076f0 EFLAGS: 00010293
RAX: ffffffff81fd00bb RBX: ffff88805b528ae0 RCX: ffff88807ec48000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90018d07b01 R08: ffff88805b528ae7 R09: 1ffff1100b6a515c
R10: dffffc0000000000 R11: ffffed100b6a515d R12: 1ffff1100be101c1
R13: ffff88805f080e18 R14: ffff88805f0807a0 R15: 1ffff1100be101c3
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4b201f6000 CR3: 000000005c484000 CR4: 00000000003506e0
Call Trace:
<TASK>
nilfs_segctor_collect_dirty_files fs/nilfs2/segment.c:2009 [inline]
nilfs_segctor_do_construct+0x32c/0x6870 fs/nilfs2/segment.c:2071
nilfs_segctor_construct+0x17b/0x690 fs/nilfs2/segment.c:2454
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2562 [inline]
nilfs_segctor_thread+0x4f6/0x1000 fs/nilfs2/segment.c:2646
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 59a2de10b81a Linux 6.6.97
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=108cfe8c580000

kernel config: https://syzkaller.appspot.com/x/.config?x=ac0b29aca872266f
dashboard link: https://syzkaller.appspot.com/bug?extid=1d3cc35f66cd8ede91bf
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10aafbd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126eed82580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/32864b54a55c/disk-59a2de10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b0bbe4ada642/vmlinux-59a2de10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e3fe91e14c2/bzImage-59a2de10.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/fd8b46d407d2/mount_0.gz

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

------------[ cut here ]------------

WARNING: CPU: 1 PID: 6023 at fs/buffer.c:1188 mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Modules linked in:
CPU: 1 PID: 6023 Comm: segctord Not tainted 6.6.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/19/2025

RIP: 0010:mark_buffer_dirty+0x2bb/0x4d0 fs/buffer.c:1188
Code: 00 00 00 5b 41 5c 41 5e 41 5f 5d e9 ef ac fc ff e8 ca 95 88 ff 48 89 df 5b 41 5c 41 5e 41 5f 5d e9 fa 57 e8 ff e8 b5 95 88 ff <0f> 0b e9 84 fd ff ff e8 a9 95 88 ff 0f 0b e9 b0 fd ff ff e8 9d 95

RSP: 0018:ffffc900036d76f0 EFLAGS: 00010293

RAX: ffffffff81fd00bb RBX: ffff888060268740 RCX: ffff888026a79e00

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002

RBP: ffffc900036d7b01 R08: ffff888060268747 R09: 1ffff1100c04d0e8
R10: dffffc0000000000 R11: ffffed100c04d0e9 R12: 1ffff1100b6174f5
R13: ffff88805b0ba7b8 R14: ffff88805b0ba140 R15: 1ffff1100b6174f7

FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007fefb0344000 CR3: 00000000262e1000 CR4: 00000000003506e0

Call Trace:
<TASK>
nilfs_segctor_collect_dirty_files fs/nilfs2/segment.c:2009 [inline]
nilfs_segctor_do_construct+0x32c/0x6870 fs/nilfs2/segment.c:2071
nilfs_segctor_construct+0x17b/0x690 fs/nilfs2/segment.c:2454
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2562 [inline]
nilfs_segctor_thread+0x4f6/0x1000 fs/nilfs2/segment.c:2646
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---

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.