EXT4-fs error (device sda1): ext4_xattr_set_entry:1603: inode #16595: comm syz-executor.5: corrupted xattr entries
EXT4-fs error (device sda1): ext4_xattr_set_entry:1603: inode #16595: comm syz-executor.5: corrupted xattr entries
EXT4-fs error (device sda1): ext4_xattr_set_entry:1603: inode #16595: comm syz-executor.5: corrupted xattr entries
==================================================================
BUG: KASAN: slab-out-of-bounds in memset include/linux/string.h:337 [inline]
BUG: KASAN: slab-out-of-bounds in __ext4_expand_extra_isize+0x16c/0x240 fs/ext4/inode.c:5914
Write of size 2015 at addr ffff88806416efa0 by task syz-executor.5/4066

CPU: 0 PID: 4066 Comm: syz-executor.5 Not tainted 5.1.0-rc1+ #32
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x172/0x1f0 lib/dump_stack.c:113
 print_address_description.cold+0x7c/0x20d mm/kasan/report.c:187
 kasan_report.cold+0x1b/0x40 mm/kasan/report.c:317
 check_memory_region_inline mm/kasan/generic.c:185 [inline]
 check_memory_region+0x123/0x190 mm/kasan/generic.c:191
 memset+0x24/0x40 mm/kasan/common.c:115
 memset include/linux/string.h:337 [inline]
 __ext4_expand_extra_isize+0x16c/0x240 fs/ext4/inode.c:5914
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5966 [inline]
 ext4_mark_inode_dirty+0x6e9/0x940 fs/ext4/inode.c:6042
 ext4_dirty_inode+0x8f/0xc0 fs/ext4/inode.c:6076
 __mark_inode_dirty+0x919/0x1290 fs/fs-writeback.c:2155
 generic_update_time+0x21c/0x370 fs/inode.c:1651
 update_time fs/inode.c:1667 [inline]
 file_update_time+0x311/0x4f0 fs/inode.c:1877
 ext4_page_mkwrite+0x1b7/0x13b0 fs/ext4/inode.c:6221
 do_page_mkwrite+0xe2/0x480 mm/memory.c:2151
 do_shared_fault mm/memory.c:3514 [inline]
 do_fault mm/memory.c:3582 [inline]
 handle_pte_fault mm/memory.c:3809 [inline]
 __handle_mm_fault+0x2b32/0x3ec0 mm/memory.c:3933
 handle_mm_fault+0x43f/0xb30 mm/memory.c:3970
 do_user_addr_fault arch/x86/mm/fault.c:1475 [inline]
 __do_page_fault+0x5ef/0xda0 arch/x86/mm/fault.c:1541
 do_page_fault+0x71/0x581 arch/x86/mm/fault.c:1572
 page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1143
RIP: 0033:0x4016b7
Code: 00 00 00 48 83 ec 08 48 8b 15 fd ed 64 00 48 8b 05 ee ed 64 00 48 39 d0 48 8d 8a 00 00 00 01 72 17 48 39 c8 73 12 48 8d 50 04 <89> 38 48 89 15 d0 ed 64 00 48 83 c4 08 c3 48 89 c6 bf 48 78 4c 00
RSP: 002b:00007ffc6fcf0700 EFLAGS: 00010287
RAX: 0000001b2d021000 RBX: 00000000f5f89ef3 RCX: 0000001b2e020000
RDX: 0000001b2d021004 RSI: 00000000000003bf RDI: ffffffff065ac3bf
RBP: 00000000000001cc R08: 00000000065ac3bf R09: 00000000065ac3c3
R10: 00007ffc6fcf08a0 R11: 0000000000000246 R12: 000000000073bf88
R13: 0000000080000000 R14: 00007f308ac68008 R15: 00000000000015e0

The buggy address belongs to the page:
page:ffffea0001905b80 count:2 mapcount:0 mapping:ffff88809fcdfad8 index:0x429
def_blk_aops 
flags: 0x1fffc000000207a(referenced|dirty|lru|active|workingset|private)
raw: 01fffc000000207a ffffea0000266348 ffffea00023e9b48 ffff88809fcdfad8
raw: 0000000000000429 ffff88809734e9d8 00000002ffffffff ffff8880aa204bc0
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff8880aa204bc0

Memory state around the buggy address:
 ffff88806416ef00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88806416ef80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88806416f000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
                   ^
 ffff88806416f080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88806416f100: fb fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc
==================================================================