new mount options do not match the existing superblock, will be ignored ================================================================== BUG: KASAN: slab-out-of-bounds in hfs_asc2mac+0x68f/0x710 fs/hfs/trans.c:133 Write of size 1 at addr ffff8880a8883fce by task syz-executor.1/18730 CPU: 0 PID: 18730 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354 kasan_report mm/kasan/report.c:412 [inline] __asan_report_store1_noabort+0x88/0x90 mm/kasan/report.c:435 hfs_asc2mac+0x68f/0x710 fs/hfs/trans.c:133 hfs_cat_build_key+0xbe/0x1a0 fs/hfs/catalog.c:28 hfs_lookup+0x1c2/0x300 fs/hfs/dir.c:31 __lookup_slow+0x246/0x4a0 fs/namei.c:1672 lookup_slow fs/namei.c:1689 [inline] walk_component+0x7ac/0xda0 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat+0x1ff/0x8d0 fs/namei.c:2319 filename_lookup+0x1ac/0x5a0 fs/namei.c:2349 user_path_at include/linux/namei.h:57 [inline] path_setxattr+0x95/0x190 fs/xattr.c:534 __do_sys_setxattr fs/xattr.c:554 [inline] __se_sys_setxattr fs/xattr.c:550 [inline] __x64_sys_setxattr+0xc0/0x160 fs/xattr.c:550 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7fca977e50d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fca8d93e168 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc RAX: ffffffffffffffda RBX: 00007fca97905050 RCX: 00007fca977e50d9 RDX: 0000000020000700 RSI: 0000000020000240 RDI: 0000000020000640 RBP: 00007fca97840ae9 R08: 0000000000000003 R09: 0000000000000000 R10: 0000000000000016 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fff9034e98f R14: 00007fca8d93e300 R15: 0000000000022000 Allocated by task 18730: __do_kmalloc mm/slab.c:3727 [inline] __kmalloc+0x15a/0x3c0 mm/slab.c:3736 kmalloc include/linux/slab.h:520 [inline] hfs_find_init+0x91/0x230 fs/hfs/bfind.c:21 hfs_lookup+0xfe/0x300 fs/hfs/dir.c:28 __lookup_slow+0x246/0x4a0 fs/namei.c:1672 lookup_slow fs/namei.c:1689 [inline] walk_component+0x7ac/0xda0 fs/namei.c:1811 lookup_last fs/namei.c:2274 [inline] path_lookupat+0x1ff/0x8d0 fs/namei.c:2319 filename_lookup+0x1ac/0x5a0 fs/namei.c:2349 user_path_at include/linux/namei.h:57 [inline] path_setxattr+0x95/0x190 fs/xattr.c:534 __do_sys_setxattr fs/xattr.c:554 [inline] __se_sys_setxattr fs/xattr.c:550 [inline] __x64_sys_setxattr+0xc0/0x160 fs/xattr.c:550 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 0: (stack is not available) The buggy address belongs to the object at ffff8880a8883f80 which belongs to the cache kmalloc-96 of size 96 The buggy address is located 78 bytes inside of 96-byte region [ffff8880a8883f80, ffff8880a8883fe0) The buggy address belongs to the page: page:ffffea0002a220c0 count:1 mapcount:0 mapping:ffff88813bff04c0 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffffea0002844088 ffff88813bff1448 ffff88813bff04c0 raw: 0000000000000000 ffff8880a8883000 0000000100000020 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880a8883e80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff8880a8883f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff8880a8883f80: 00 00 00 00 00 00 00 00 00 06 fc fc fc fc fc fc ^ ffff8880a8884000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff8880a8884080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================