REISERFS (device loop4): checking transaction log (loop4)
REISERFS (device loop4): Using r5 hash to sort names
==================================================================
BUG: KASAN: use-after-free in set_de_name_and_namelen fs/reiserfs/namei.c:81 [inline]
BUG: KASAN: use-after-free in linear_search_in_dir_item fs/reiserfs/namei.c:262 [inline]
BUG: KASAN: use-after-free in reiserfs_find_entry+0xac8/0x149c fs/reiserfs/namei.c:331
Read of size 1 at addr ffff00013cf02ecb by task syz-executor.4/16398

CPU: 1 PID: 16398 Comm: syz-executor.4 Not tainted 6.4.0-rc7-syzkaller-g42234a752679 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call trace:
 dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:233
 show_stack+0x2c/0x44 arch/arm64/kernel/stacktrace.c:240
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:351 [inline]
 print_report+0x174/0x514 mm/kasan/report.c:462
 kasan_report+0xd4/0x130 mm/kasan/report.c:572
 __asan_report_load1_noabort+0x20/0x2c mm/kasan/report_generic.c:378
 set_de_name_and_namelen fs/reiserfs/namei.c:81 [inline]
 linear_search_in_dir_item fs/reiserfs/namei.c:262 [inline]
 reiserfs_find_entry+0xac8/0x149c fs/reiserfs/namei.c:331
 reiserfs_lookup+0x17c/0x45c fs/reiserfs/namei.c:368
 __lookup_slow+0x250/0x374 fs/namei.c:1690
 lookup_one_len+0x178/0x28c fs/namei.c:2742
 reiserfs_lookup_privroot+0x8c/0x184 fs/reiserfs/xattr.c:976
 reiserfs_fill_super+0x15b4/0x2028 fs/reiserfs/super.c:2192
 mount_bdev+0x274/0x370 fs/super.c:1380
 get_super_block+0x44/0x58 fs/reiserfs/super.c:2601
 legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
 vfs_get_tree+0x90/0x274 fs/super.c:1510
 do_new_mount+0x25c/0x8c4 fs/namespace.c:3039
 path_mount+0x590/0xe04 fs/namespace.c:3369
 do_mount fs/namespace.c:3382 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x244 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:191
 el0_svc+0x4c/0x160 arch/arm64/kernel/entry-common.c:647
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:665
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591

The buggy address belongs to the physical page:
page:0000000034d96597 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x17cf02
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 05ffc00000000000 dead000000000100 dead000000000122 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff00013cf02d80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff00013cf02e00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff00013cf02e80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                              ^
 ffff00013cf02f00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff00013cf02f80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================