ci2 starts bisection 2024-09-12 02:44:08.485658206 +0000 UTC m=+28338.404743021
bisecting fixing commit since ca87e77a2ef8b298aa9f69658d5898e72ee450fe
building syzkaller on f3921d4d63f97d1f1fb49a69ea85744bb7ef184b
ensuring issue is reproducible on original commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe

testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 0a7690ff4e10caf9e876e3b1bff6fd6b8209e881c83c96b887cc8cb9701200af
run #0: crashed: KASAN: use-after-free Read in ext4_search_dir
run #1: crashed: KASAN: use-after-free Read in ext4_search_dir
run #2: crashed: KASAN: use-after-free Read in ext4_search_dir
run #3: crashed: KASAN: use-after-free Read in ext4_search_dir
run #4: crashed: KASAN: use-after-free Read in ext4_search_dir
run #5: crashed: KASAN: use-after-free Read in ext4_search_dir
run #6: crashed: KASAN: use-after-free Read in ext4_search_dir
run #7: crashed: KASAN: use-after-free Read in ext4_search_dir
run #8: crashed: KASAN: use-after-free Read in ext4_search_dir
run #9: crashed: KASAN: use-after-free Read in ext4_search_dir
run #10: crashed: KASAN: use-after-free Read in ext4_search_dir
run #11: crashed: KASAN: use-after-free Read in ext4_search_dir
run #12: crashed: KASAN: use-after-free Read in ext4_search_dir
run #13: crashed: KASAN: use-after-free Read in ext4_search_dir
run #14: crashed: KASAN: use-after-free Read in ext4_search_dir
run #15: crashed: KASAN: use-after-free Read in ext4_search_dir
run #16: crashed: KASAN: use-after-free Read in ext4_search_dir
run #17: crashed: KASAN: use-after-free Read in ext4_search_dir
run #18: crashed: KASAN: use-after-free Read in ext4_search_dir
run #19: crashed: KASAN: slab-out-of-bounds Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
check whether we can drop unnecessary instrumentation
disabling configs for [UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG LEAK], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 90ef40ed8da044ab10485a889480f9141dd17634d6e027b4bf5c21faf77f5d33
all runs: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the bug reproduces without the instrumentation
disabling configs for [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed
kconfig minimization: base=3824 full=7523 leaves diff=1996
split chunks (needed=false): <1996>
split chunk #0 of len 1996 into 5 parts
testing without sub-chunk 1/5
disabling configs for [ATOMIC_SLEEP HANG LEAK UBSAN BUG LOCKDEP], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 72075e0ece5c1b642c34182611d44157530aeefd72e75152e110a73eb740ee37
run #0: crashed: KASAN: use-after-free Read in ext4_search_dir
run #1: crashed: KASAN: use-after-free Read in ext4_search_dir
run #2: crashed: KASAN: use-after-free Read in ext4_search_dir
run #3: crashed: KASAN: use-after-free Read in ext4_search_dir
run #4: crashed: KASAN: out-of-bounds Read in ext4_search_dir
run #5: crashed: KASAN: use-after-free Read in ext4_search_dir
run #6: crashed: KASAN: use-after-free Read in ext4_search_dir
run #7: crashed: KASAN: use-after-free Read in ext4_search_dir
run #8: crashed: KASAN: use-after-free Read in ext4_search_dir
run #9: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the chunk can be dropped
testing without sub-chunk 2/5
disabling configs for [BUG LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 68172fc58392f1c3ecd2d5d96777ac8fa9f1a8367487073cbc701d45286c5fa8
run #0: crashed: KASAN: use-after-free Read in ext4_search_dir
run #1: crashed: KASAN: use-after-free Read in ext4_search_dir
run #2: crashed: KASAN: use-after-free Read in ext4_search_dir
run #3: crashed: KASAN: use-after-free Read in ext4_search_dir
run #4: crashed: KASAN: use-after-free Read in ext4_search_dir
run #5: crashed: KASAN: out-of-bounds Read in ext4_search_dir
run #6: crashed: KASAN: use-after-free Read in ext4_search_dir
run #7: crashed: KASAN: use-after-free Read in ext4_search_dir
run #8: crashed: KASAN: use-after-free Read in ext4_search_dir
run #9: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the chunk can be dropped
testing without sub-chunk 3/5
disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 1af98a3e7254c725b9d2758327ba943546350baac8ee4772f6bd3eae1cba55a5
all runs: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the chunk can be dropped
testing without sub-chunk 4/5
disabling configs for [LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP HANG], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 88405a6438abf9aa1b5a186d041c0dbb41a66f2de2b4651cb9ab603df4563293
run #0: crashed: KASAN: use-after-free Read in ext4_search_dir
run #1: crashed: KASAN: use-after-free Read in ext4_search_dir
run #2: crashed: KASAN: use-after-free Read in ext4_search_dir
run #3: crashed: KASAN: use-after-free Read in ext4_search_dir
run #4: crashed: KASAN: use-after-free Read in ext4_search_dir
run #5: crashed: KASAN: use-after-free Read in ext4_search_dir
run #6: crashed: KASAN: use-after-free Read in ext4_search_dir
run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_search_dir
run #8: crashed: KASAN: use-after-free Read in ext4_search_dir
run #9: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the chunk can be dropped
testing without sub-chunk 5/5
disabling configs for [HANG LEAK UBSAN BUG LOCKDEP ATOMIC_SLEEP], they are not needed
testing commit ca87e77a2ef8b298aa9f69658d5898e72ee450fe gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: a71fcbc6906ffa6b98530c419ba781caf59b6128b1acc7d8a69238dc41b67ae0
all runs: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
the chunk can be dropped
disabling configs for [LOCKDEP ATOMIC_SLEEP HANG LEAK UBSAN BUG], they are not needed
testing current HEAD 5ca5b389fddfe4ce3a698cbc1321fac3d8e3e5b1
testing commit 5ca5b389fddfe4ce3a698cbc1321fac3d8e3e5b1 gcc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
kernel signature: 37957a0848108e71593e3916fa0c6510ef734e5b4aededeb9b6223d4926d3b64
all runs: crashed: KASAN: use-after-free Read in ext4_search_dir
representative crash: KASAN: use-after-free Read in ext4_search_dir, types: [KASAN]
crash still not fixed/happens on the oldest tested release
revisions tested: 8, total time: 1h22m36.920268044s (build: 43m49.960633493s, test: 35m50.529662018s)
crash still not fixed or there were kernel test errors
commit msg: Linux 6.1.109
crash: KASAN: use-after-free Read in ext4_search_dir
EXT4-fs: Ignoring removed bh option
EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem
EXT4-fs (loop0): 1 truncate cleaned up
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: none.
==================================================================
BUG: KASAN: use-after-free in ext4_search_dir+0x148/0x250 fs/ext4/namei.c:1544
Read of size 1 at addr ffff8881239363ed by task syz-executor.0/1400

CPU: 1 PID: 1400 Comm: syz-executor.0 Not tainted 6.1.109-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xf4/0x251 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:284 [inline]
 print_report+0x15f/0x4f0 mm/kasan/report.c:395
 kasan_report+0x136/0x160 mm/kasan/report.c:495
 ext4_search_dir+0x148/0x250 fs/ext4/namei.c:1544
 ext4_find_inline_entry+0x367/0x540 fs/ext4/inline.c:1726
 __ext4_find_entry+0x2dc/0x1a10 fs/ext4/namei.c:1617
 ext4_lookup_entry fs/ext4/namei.c:1772 [inline]
 ext4_lookup+0x1ab/0x5f0 fs/ext4/namei.c:1840
 lookup_open fs/namei.c:3462 [inline]
 open_last_lookups fs/namei.c:3552 [inline]
 path_openat+0xdb6/0x2410 fs/namei.c:3782
 do_filp_open+0x226/0x430 fs/namei.c:3812
 do_sys_openat2+0x10b/0x3f0 fs/open.c:1318
 do_sys_open fs/open.c:1334 [inline]
 __do_sys_open fs/open.c:1342 [inline]
 __se_sys_open fs/open.c:1338 [inline]
 __x64_sys_open+0x1eb/0x240 fs/open.c:1338
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0x80 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f537a105b29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5379c880c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f537a224f80 RCX: 00007f537a105b29
RDX: 0000000000000000 RSI: 0000000000141042 RDI: 0000000020000100
RBP: 00007f537a15147a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000006 R14: 00007f537a224f80 R15: 00007ffc8a70d248
 </TASK>

The buggy address belongs to the physical page:
page:ffffea00048e4d80 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x123936
flags: 0x200000000000000(node=0|zone=2)
raw: 0200000000000000 ffffea00048e4dc8 ffffea00048e4d48 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
 ffff888123936280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888123936300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888123936380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                                          ^
 ffff888123936400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888123936480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================