[v6.1] kernel BUG in set_blocksize

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 81e1dc2f7001 Linux 6.1.79
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14c42dd8180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1f1b2df4155f9cc0
dashboard link: https://syzkaller.appspot.com/bug?extid=8ba2e4074becfc42a08e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c15e68f002df/disk-81e1dc2f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/48d036ef2f3c/vmlinux-81e1dc2f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f372bf435776/bzImage-81e1dc2f.xz

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

nilfs_fill_super+0xe9/0x660 fs/nilfs2/super.c:1078
nilfs_mount+0x679/0x9a0 fs/nilfs2/super.c:1347
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x2ba/0xb40 fs/namespace.c:3051
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3579
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
------------[ cut here ]------------
kernel BUG at mm/truncate.c:423!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 29802 Comm: syz-executor.2 Not tainted 6.1.79-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:truncate_inode_pages_range+0x110a/0x1340 mm/truncate.c:423
Code: 00 00 48 c7 c7 10 2c 1d 8d 48 89 da e8 9f 3e a5 02 e9 e9 f5 ff ff e8 45 ae cc ff 4c 89 e7 48 c7 c6 00 2d f5 8a e8 36 59 0c 00 <0f> 0b e8 2f ae cc ff 4c 89 e7 48 c7 c6 20 2c f5 8a e8 20 59 0c 00
RSP: 0018:ffffc900033bf6c0 EFLAGS: 00010246
RAX: bb440468f19bd000 RBX: 000000000000007f RCX: ffffc900033bf503
RDX: 0000000000000002 RSI: ffffffff8aebfec0 RDI: ffffffff8b3d1040
RBP: ffffc900033bf8f0 R08: dffffc0000000000 R09: fffffbfff1ce68c6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0000794f80
R13: ffffc900033bf778 R14: ffffc900033bf810 R15: 0000000000000003
FS: 00007f96e63ec6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2c561ad988 CR3: 0000000074a91000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kill_bdev block/bdev.c:76 [inline]
set_blocksize+0x2d9/0x350 block/bdev.c:152
sb_set_blocksize block/bdev.c:161 [inline]
sb_min_blocksize+0xb7/0x170 block/bdev.c:177
init_nilfs+0xbc/0x790 fs/nilfs2/the_nilfs.c:679
nilfs_fill_super+0xe9/0x660 fs/nilfs2/super.c:1078
nilfs_mount+0x679/0x9a0 fs/nilfs2/super.c:1347
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x2ba/0xb40 fs/namespace.c:3051
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3579
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f96e567f4aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f96e63ebef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f96e63ebf80 RCX: 00007f96e567f4aa
RDX: 0000000020000ec0 RSI: 0000000020000f00 RDI: 00007f96e63ebf40
RBP: 0000000020000ec0 R08: 00007f96e63ebf80 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000f00
R13: 00007f96e63ebf40 R14: 0000000000000eb0 R15: 0000000020000f40
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:truncate_inode_pages_range+0x110a/0x1340 mm/truncate.c:423
Code: 00 00 48 c7 c7 10 2c 1d 8d 48 89 da e8 9f 3e a5 02 e9 e9 f5 ff ff e8 45 ae cc ff 4c 89 e7 48 c7 c6 00 2d f5 8a e8 36 59 0c 00 <0f> 0b e8 2f ae cc ff 4c 89 e7 48 c7 c6 20 2c f5 8a e8 20 59 0c 00
RSP: 0018:ffffc900033bf6c0 EFLAGS: 00010246
RAX: bb440468f19bd000 RBX: 000000000000007f RCX: ffffc900033bf503
RDX: 0000000000000002 RSI: ffffffff8aebfec0 RDI: ffffffff8b3d1040
RBP: ffffc900033bf8f0 R08: dffffc0000000000 R09: fffffbfff1ce68c6
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0000794f80
R13: ffffc900033bf778 R14: ffffc900033bf810 R15: 0000000000000003
FS: 00007f96e63ec6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555595a788 CR3: 0000000074a91000 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 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