[v6.1] kernel BUG in folio_end_writeback

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f15aa8280000
kernel config: https://syzkaller.appspot.com/x/.config?x=47d3bbfdb3b1ddd2
dashboard link: https://syzkaller.appspot.com/bug?extid=9e4e1f20842b370492b4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13b5bb14280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1396af18280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/658765c915fa/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d69e8a1aff2d/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0317a9546209/bzImage-ca48fc16.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/03cc29b78a45/mount_0.gz

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

NILFS (loop5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
kernel BUG at mm/filemap.c:1614!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3972 Comm: segctord Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:folio_end_writeback+0x432/0x6f0 mm/filemap.c:1614
Code: 84 d3 00 00 00 e8 6e 7b d3 ff e9 4c fc ff ff e8 64 7b d3 ff 4c 89 ff 48 c7 c6 e0 c8 f4 8a e8 f5 55 12 00 0f 0b e8 4e 7b d3 ff <0f> 0b e8 47 7b d3 ff 4c 89 ff 48 c7 c6 a0 c8 f4 8a e8 d8 55 12 00
RSP: 0018:ffffc9000479f6b8 EFLAGS: 00010293
RAX: ffffffff81b64d72 RBX: 0000000000000081 RCX: ffff88807d0bd7c0
RDX: 0000000000000000 RSI: ffffffff8aebe1a0 RDI: ffffffff8b3cbfa0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ca5da6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0001e47ff4
R13: 1ffffd40003c8ffe R14: ffffea0001e47fc8 R15: ffffea0001e47fc0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f09284f8718 CR3: 0000000020cc5000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_segctor_complete_write fs/nilfs2/segment.c:1888 [inline]
nilfs_segctor_wait fs/nilfs2/segment.c:1949 [inline]
nilfs_segctor_do_construct+0x5245/0x6c70 fs/nilfs2/segment.c:2112
nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2399
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2507 [inline]
nilfs_segctor_thread+0x536/0x1130 fs/nilfs2/segment.c:2590
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_end_writeback+0x432/0x6f0 mm/filemap.c:1614
Code: 84 d3 00 00 00 e8 6e 7b d3 ff e9 4c fc ff ff e8 64 7b d3 ff 4c 89 ff 48 c7 c6 e0 c8 f4 8a e8 f5 55 12 00 0f 0b e8 4e 7b d3 ff <0f> 0b e8 47 7b d3 ff 4c 89 ff 48 c7 c6 a0 c8 f4 8a e8 d8 55 12 00
RSP: 0018:ffffc9000479f6b8 EFLAGS: 00010293
RAX: ffffffff81b64d72 RBX: 0000000000000081 RCX: ffff88807d0bd7c0
RDX: 0000000000000000 RSI: ffffffff8aebe1a0 RDI: ffffffff8b3cbfa0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ca5da6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0001e47ff4
R13: 1ffffd40003c8ffe R14: ffffea0001e47fc8 R15: ffffea0001e47fc0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f093081a000 CR3: 0000000026eec000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 bug is already fixed, 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 change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

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

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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.