EXT4-fs (loop2): 1 truncate cleaned up
EXT4-fs (loop2): mounted filesystem without journal. Quota mode: none.
==================================================================
BUG: KASAN: out-of-bounds in ext4_xattr_set_entry+0x83c/0x15f4 fs/ext4/xattr.c:1710
Read of size 18446744073709551600 at addr ffff0000ea1ffeb8 by task syz.2.190/5430

CPU: 1 PID: 5430 Comm: syz.2.190 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/07/2026
Call trace:
 dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106
 print_address_description+0x88/0x218 mm/kasan/report.c:316
 print_report+0x50/0x68 mm/kasan/report.c:420
 kasan_report+0xa8/0xfc mm/kasan/report.c:524
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x258/0x290 mm/kasan/generic.c:189
 memmove+0x48/0x90 mm/kasan/shadow.c:54
 ext4_xattr_set_entry+0x83c/0x15f4 fs/ext4/xattr.c:1710
 ext4_xattr_ibody_set+0x208/0x604 fs/ext4/xattr.c:2219
 ext4_destroy_inline_data_nolock+0x1c8/0x4a8 fs/ext4/inline.c:468
 ext4_convert_inline_data_to_extent fs/ext4/inline.c:628 [inline]
 ext4_try_to_write_inline_data+0x5d4/0x11a0 fs/ext4/inline.c:769
 ext4_write_begin+0x234/0x12d4 fs/ext4/inode.c:1206
 generic_perform_write+0x240/0x508 mm/filemap.c:3862
 ext4_buffered_write_iter+0x2c0/0x520 fs/ext4/file.c:285
 ext4_file_write_iter+0x188/0x1500 fs/ext4/file.c:-1
 do_iter_readv_writev fs/read_write.c:-1 [inline]
 do_iter_write+0x520/0x93c fs/read_write.c:861
 vfs_writev fs/read_write.c:934 [inline]
 do_pwritev+0x1e8/0x338 fs/read_write.c:1031
 __do_sys_pwritev2 fs/read_write.c:1090 [inline]
 __se_sys_pwritev2 fs/read_write.c:1081 [inline]
 __arm64_sys_pwritev2+0xdc/0x110 fs/read_write.c:1081
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x128 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

The buggy address belongs to the physical page:
page:000000008da3ed43 refcount:2 mapcount:0 mapping:00000000895c89f6 index:0x8 pfn:0x12a1ff
memcg:ffff0000c0940000
aops:def_blk_aops ino:700002
flags: 0x5ffd6000002205e(referenced|uptodate|dirty|lru|workingset|private|mappedtodisk|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffd6000002205e fffffc0003a88008 fffffc00033a1cc8 ffff0000c049e018
raw: 0000000000000008 ffff0000fbc193a0 00000002ffffffff ffff0000c0940000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000ea1ffd80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000ea1ffe00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000ea1ffe80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                        ^
 ffff0000ea1fff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000ea1fff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================
EXT4-fs error (device loop2): ext4_read_block_bitmap_nowait:477: comm syz.2.190: Invalid block bitmap block 0 in block_group 0