[syzbot] [ext4?] [reiserfs?] kernel BUG in __phys_addr (2)

Hello,

syzbot found the following issue on:

HEAD commit:    8e4b7f2f3d60 Add linux-next specific files for 20230711
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=132602caa80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=eaa6217eed71d333
dashboard link: https://syzkaller.appspot.com/bug?extid=daa1128e28d3c3961cb2
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11605074a80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14f723e2a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/52debf037744/disk-8e4b7f2f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7b4580012911/vmlinux-8e4b7f2f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/79b0de8a559f/bzImage-8e4b7f2f.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c865e2933fcf/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
kernel BUG at arch/x86/mm/physaddr.c:28!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5041 Comm: syz-executor387 Not tainted 6.5.0-rc1-next-20230711-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:__phys_addr+0xd7/0x140 arch/x86/mm/physaddr.c:28
Code: e3 44 89 e9 31 ff 48 d3 eb 48 89 de e8 02 ec 4a 00 48 85 db 75 0f e8 b8 ef 4a 00 4c 89 e0 5b 5d 41 5c 41 5d c3 e8 a9 ef 4a 00 <0f> 0b e8 a2 ef 4a 00 48 c7 c0 10 e0 79 8c 48 ba 00 00 00 00 00 fc
RSP: 0018:ffffc900039feeb0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 06100164000013b6 RCX: 0000000000000000
RDX: ffff88807e7f1dc0 RSI: ffffffff813a2f67 RDI: 0000000000000006
RBP: 06100164800013b6 R08: 0000000000000006 R09: 06100164800013b6
R10: 061078e4000013b6 R11: 0000000000000001 R12: 061078e4000013b6
R13: ffffc900039fef18 R14: 06100164000013b6 R15: 0000000000000000
FS:  000055555695c480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055fb6fc92f18 CR3: 0000000074063000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 virt_to_folio include/linux/mm.h:1263 [inline]
 virt_to_slab mm/kasan/../slab.h:213 [inline]
 qlink_to_cache mm/kasan/quarantine.c:129 [inline]
 qlist_free_all+0x86/0x170 mm/kasan/quarantine.c:182
 kasan_quarantine_reduce+0x195/0x220 mm/kasan/quarantine.c:292
 __kasan_slab_alloc+0x63/0x90 mm/kasan/common.c:305
 kasan_slab_alloc include/linux/kasan.h:186 [inline]
 slab_post_alloc_hook mm/slab.h:762 [inline]
 slab_alloc_node mm/slub.c:3470 [inline]
 slab_alloc mm/slub.c:3478 [inline]
 __kmem_cache_alloc_lru mm/slub.c:3485 [inline]
 kmem_cache_alloc+0x173/0x390 mm/slub.c:3494
 kmem_cache_zalloc include/linux/slab.h:693 [inline]
 jbd2_alloc_handle include/linux/jbd2.h:1602 [inline]
 new_handle fs/jbd2/transaction.c:476 [inline]
 jbd2__journal_start+0x190/0x850 fs/jbd2/transaction.c:503
 __ext4_journal_start_sb+0x411/0x5d0 fs/ext4/ext4_jbd2.c:111
 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
 ext4_dirty_inode+0xa5/0x130 fs/ext4/inode.c:5919
 __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2430
 mark_inode_dirty include/linux/fs.h:2150 [inline]
 generic_write_end+0x354/0x440 fs/buffer.c:2317
 ext4_da_write_end+0x1f9/0xb50 fs/ext4/inode.c:2988
 generic_perform_write+0x331/0x5d0 mm/filemap.c:3936
 ext4_buffered_write_iter+0x123/0x3d0 fs/ext4/file.c:299
 ext4_file_write_iter+0x8f2/0x1880 fs/ext4/file.c:722
 __kernel_write_iter+0x262/0x7e0 fs/read_write.c:517
 dump_emit_page fs/coredump.c:888 [inline]
 dump_user_range+0x23c/0x710 fs/coredump.c:915
 elf_core_dump+0x27f4/0x3790 fs/binfmt_elf.c:2142
 do_coredump+0x2f44/0x4050 fs/coredump.c:764
 get_signal+0x1c16/0x2650 kernel/signal.c:2875
 arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:309
 exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
 exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204
 irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:310
 exc_page_fault+0xc0/0x170 arch/x86/mm/fault.c:1568
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7f92da04d4f3
Code: 3f 00 00 77 02 c3 90 48 89 77 20 31 c0 c3 66 0f 1f 84 00 00 00 00 00 41 55 41 54 55 53 48 83 ec 08 64 48 8b 04 25 10 00 00 00 <4c> 8b a0 98 06 00 00 4c 03 a0 90 06 00 00 4c 29 e6 64 48 8b 1c 25
RSP: 002b:00007fffbd381320 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000001 RCX: 00007f92da0a4af5
RDX: 0000000000000006 RSI: 00007fffbd381348 RDI: 00007f92da1025b0
RBP: 00007f92da1025b0 R08: 0000000000000000 R09: 00007fffbd588080
R10: 0000000000000000 R11: 0000000000000293 R12: 00007fffbd47ebf0
R13: 000000000001ef5f R14: 00007fffbd47ec30 R15: 0000000000000004
 </TASK>
Modules linked in:


---
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 [email protected].

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