EXT4-fs error (device sda1): ext4_xattr_ibody_get:592: inode #16543: comm syz-executor1: corrupted in-inode xattr
audit: type=1800 audit(1543760217.992:550): pid=14148 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor5" name="bus" dev="loop5" ino=1636 res=0
==================================================================
BUG: KASAN: use-after-free in memset include/linux/string.h:337 [inline]
BUG: KASAN: use-after-free in __ext4_expand_extra_isize+0x16f/0x240 fs/ext4/inode.c:5897
Write of size 10641 at addr ffff8881aa0175a0 by task syz-executor3/6092
overlayfs: filesystem on './file0' not supported as upperdir

CPU: 1 PID: 6092 Comm: syz-executor3 Not tainted 4.20.0-rc4+ #359
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+0x244/0x39d lib/dump_stack.c:113
 print_address_description.cold.7+0x9/0x1ff mm/kasan/report.c:256
 kasan_report_error mm/kasan/report.c:354 [inline]
 kasan_report.cold.8+0x242/0x309 mm/kasan/report.c:412
 check_memory_region_inline mm/kasan/kasan.c:260 [inline]
 check_memory_region+0x13e/0x1b0 mm/kasan/kasan.c:267
 memset+0x23/0x40 mm/kasan/kasan.c:285
 memset include/linux/string.h:337 [inline]
 __ext4_expand_extra_isize+0x16f/0x240 fs/ext4/inode.c:5897
 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5949 [inline]
 ext4_mark_inode_dirty+0x8f9/0xb20 fs/ext4/inode.c:6025
 ext4_dirty_inode+0x97/0xc0 fs/ext4/inode.c:6059
 __mark_inode_dirty+0x7c3/0x1510 fs/fs-writeback.c:2122
 generic_update_time+0x26a/0x450 fs/inode.c:1654
 update_time fs/inode.c:1670 [inline]
 touch_atime+0x29c/0x320 fs/inode.c:1741
 file_accessed include/linux/fs.h:2156 [inline]
 iterate_dir+0x370/0x5d0 fs/readdir.c:56
 __do_sys_getdents fs/readdir.c:231 [inline]
 __se_sys_getdents fs/readdir.c:212 [inline]
 __x64_sys_getdents+0x29f/0x510 fs/readdir.c:212
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45594b
Code: 02 74 b6 31 f6 eb b9 0f 1f 84 00 00 00 00 00 41 57 41 56 48 63 ff 41 55 41 54 b8 4e 00 00 00 55 53 48 89 f3 48 83 ec 08 0f 05 <48> 3d 00 f0 ff ff 77 55 4c 8d 24 06 49 89 c5 4c 39 e6 73 33 90 0f
RSP: 002b:00007ffcf25c9ea0 EFLAGS: 00000206 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00000000023269b0 RCX: 000000000045594b
RDX: 0000000000008000 RSI: 00000000023269b0 RDI: 0000000000000004
RBP: 00000000023269b0 R08: 0000000000000000 R09: 000000000000000c
R10: 0000000000000005 R11: 0000000000000206 R12: ffffffffffffffd4
R13: 0000000000000016 R14: 0000000000000000 R15: 0000000000000003

The buggy address belongs to the page:
page:ffffea0006a805c0 count:2 mapcount:0 mapping:ffff8881cd0b7658 index:0x42b
flags: 0x2fffc000000203a(referenced|dirty|lru|active|private)
raw: 02fffc000000203a ffffea0006a33348 ffffea00066f4048 ffff8881cd0b7658
raw: 000000000000042b ffff8881b25b19d8 00000002ffffffff ffff8881c34d6c00
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff8881c34d6c00

Memory state around the buggy address:
 ffff8881aa018f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8881aa018f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881aa019000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff8881aa019080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff8881aa019100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================