==================================================================
BUG: KASAN: slab-out-of-bounds in __jfs_setxattr+0x321/0xe00 fs/jfs/xattr.c:766
Write of size 1 at addr ffff88009594ffa3 by task syz-executor3/14925

CPU: 3 PID: 14925 Comm: syz-executor3 Not tainted 4.17.0-rc4+ #13
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+0x148/0x1b5 lib/dump_stack.c:113
 print_address_description+0x73/0x250 mm/kasan/report.c:256
 kasan_report_error mm/kasan/report.c:354 [inline]
 kasan_report+0x23f/0x360 mm/kasan/report.c:412
 __asan_report_store1_noabort+0x17/0x20 mm/kasan/report.c:435
 __jfs_setxattr+0x321/0xe00 fs/jfs/xattr.c:766
 __jfs_xattr_set+0x83/0xe0 fs/jfs/xattr.c:928
 jfs_xattr_set+0x41/0x50 fs/jfs/xattr.c:951
 __vfs_setxattr+0x9e/0xd0 fs/xattr.c:150
 __vfs_setxattr_noperm+0x102/0x390 fs/xattr.c:181
 vfs_setxattr+0xd3/0xe0 fs/xattr.c:224
 setxattr+0x214/0x2d0 fs/xattr.c:453
 path_setxattr+0x158/0x170 fs/xattr.c:472
 __do_sys_setxattr fs/xattr.c:487 [inline]
 __se_sys_setxattr fs/xattr.c:483 [inline]
 __x64_sys_setxattr+0xc4/0x150 fs/xattr.c:483
 do_syscall_64+0xda/0x560 arch/x86/entry/common.c:287
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x455a09
RSP: 002b:00007f1ec3d6bc68 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f1ec3d6c6d4 RCX: 0000000000455a09
RDX: 0000000020000000 RSI: 0000000020000080 RDI: 0000000020000180
RBP: 000000000072bea0 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000000c R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000000006b5 R14: 00000000006fe198 R15: 0000000000000000
Allocated by task 14925:
 save_stack+0x43/0xd0 mm/kasan/kasan.c:448
 set_track mm/kasan/kasan.c:460 [inline]
 kasan_kmalloc+0xae/0xe0 mm/kasan/kasan.c:553
 __do_kmalloc mm/slab.c:3718 [inline]
 __kmalloc+0x162/0x760 mm/slab.c:3727
 kmalloc include/linux/slab.h:517 [inline]
 ea_get+0x1af/0x12d0 fs/jfs/xattr.c:496
 __jfs_setxattr+0xf3/0xe00 fs/jfs/xattr.c:682
 __jfs_xattr_set+0x83/0xe0 fs/jfs/xattr.c:928
 jfs_xattr_set+0x41/0x50 fs/jfs/xattr.c:951
 __vfs_setxattr+0x9e/0xd0 fs/xattr.c:150
 __vfs_setxattr_noperm+0x102/0x390 fs/xattr.c:181
 vfs_setxattr+0xd3/0xe0 fs/xattr.c:224
 setxattr+0x214/0x2d0 fs/xattr.c:453
 path_setxattr+0x158/0x170 fs/xattr.c:472
 __do_sys_setxattr fs/xattr.c:487 [inline]
 __se_sys_setxattr fs/xattr.c:483 [inline]
 __x64_sys_setxattr+0xc4/0x150 fs/xattr.c:483
 do_syscall_64+0xda/0x560 arch/x86/entry/common.c:287
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
Freed by task 0:
(stack is not available)
The buggy address belongs to the object at ffff880095940240
 which belongs to the cache kmalloc-65536 of size 65536
The buggy address is located 64867 bytes inside of
 65536-byte region [ffff880095940240, ffff880095950240)
The buggy address belongs to the page:
page:ffffea0002565000 count:1 mapcount:0 mapping:ffff880095940240 index:0x0 compound_mapcount: 0
flags: 0x1fffc0000008100(slab|head)
raw: 01fffc0000008100 ffff880095940240 0000000000000000 0000000100000001
raw: ffffea0002548020 ffff880104801e48 ffff880104802500 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
 ffff88009594fe80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88009594ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88009594ff80: 00 00 00 00 03 fc fc fc fc fc fc fc fc fc fc fc
                               ^
 ffff880095950000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff880095950080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================