ci2 starts bisection 2025-10-11 11:23:30.920222971 +0000 UTC m=+127409.698689498
bisecting fixing commit since 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef
building syzkaller on 46eb10b79c61c4032281212d862c913683ab32a0
ensuring issue is reproducible on original commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef

testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: adb5cb068a2b10bbe36f577f8319adbca7fda9d97d6d724c8d6589b9273e5149
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #3: crashed: KASAN: use-after-free Read in ext4_read_inline_dir
run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #10: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #11: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #12: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #13: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #14: crashed: KASAN: use-after-free Read in ext4_read_inline_dir
run #15: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #16: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #17: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #18: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #19: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ]
check whether we can drop unnecessary instrumentation
disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 8e441faa07c1a22731c511d9bbd770a8a0bca4ea0c32d2934c825ea4bfe7b983
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #4: crashed: KASAN: use-after-free Read in ext4_read_inline_dir
run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_dir
run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_dir
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_dir
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_dir, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ]
the bug reproduces without the instrumentation
disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed
kconfig minimization: base=4108 full=8128 leaves diff=2157
split chunks (needed=false): <2157>
split chunk #0 of len 2157 into 5 parts
testing without sub-chunk 1/5
disabling configs for [ubsan bug_or_warning locking atomic_sleep hang memleak], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 1c5bb0f4692ae2a120ab49b52fdb73b388272d21a3a97d17a34e11f2c40d3d27
run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #1: crashed: KASAN: use-after-free Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data
run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
representative crash: KASAN: use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ]
the chunk can be dropped
testing without sub-chunk 2/5
disabling configs for [locking atomic_sleep hang memleak ubsan bug_or_warning], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 8c777807d3ea09b9e840bbafbca5d4c58171e7c3adc5fa4bf0346fa6ad3f53c6
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #5: crashed: KASAN: use-after-free Read in ext4_read_inline_data
run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ]
the chunk can be dropped
testing without sub-chunk 3/5
disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: cf8661313c9c68b1dd35460268a1ae2685e44174726965ae3620881341b838fb
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ]
the chunk can be dropped
testing without sub-chunk 4/5
disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 680d168fdff4ae91475d61a4512a0723e6a8a9b741cb77420a34ae6848112fc8
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #6: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ]
the chunk can be dropped
testing without sub-chunk 5/5
disabling configs for [bug_or_warning locking atomic_sleep hang memleak ubsan], they are not needed
testing commit 910bfc26d16d07df5a2bfcbc63f0aa9d1397e2ef gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 7afb691a7490d9c57b4467c0d76bfadb05da6d7315900c85ffdc80659f4e3998
run #0: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #1: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #5: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #6: crashed: KASAN: use-after-free Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
representative crash: KASAN: slab-out-of-bounds Read in ext4_read_inline_data, types: [KASAN-READ KASAN-USE-AFTER-FREE-READ]
the chunk can be dropped
disabling configs for [hang memleak ubsan bug_or_warning locking atomic_sleep], they are not needed
testing current HEAD 0739473694c4878513031006829f1030ec850bc2
testing commit 0739473694c4878513031006829f1030ec850bc2 gcc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
kernel signature: 8ce86c178698932ccb1c3176a8e968314511aabab78995e5cb834358c966534d
run #0: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #1: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #2: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #3: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #4: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #5: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #6: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
run #7: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #8: crashed: KASAN: slab-out-of-bounds Read in ext4_read_inline_data
run #9: crashed: KASAN: slab-use-after-free Read in ext4_read_inline_data
representative crash: KASAN: slab-use-after-free Read in ext4_read_inline_data, types: [KASAN-USE-AFTER-FREE-READ KASAN-READ]
crash still not fixed/happens on the oldest tested release
revisions tested: 8, total time: 1h58m9.872984055s (build: 1h6m46.022810124s, test: 41m40.430373601s)
crash still not fixed or there were kernel test errors
commit msg: Merge tag 'for-6.18/hpfs-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
crash: KASAN: slab-use-after-free Read in ext4_read_inline_data
EXT4-fs error (device loop0): ext4_readdir:264: inode #2: block 16: comm syz-executor: path /0/bus: bad entry in directory: rec_len is smaller than minimal - offset=980, inode=0, rec_len=0, size=1024 fake=0
==================================================================
BUG: KASAN: slab-use-after-free in ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214
Read of size 68 at addr ffff88811c30a51a by task syz-executor/2386

CPU: 1 UID: 0 PID: 2386 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0xf4/0x170 lib/dump_stack.c:120
 print_address_description mm/kasan/report.c:378 [inline]
 print_report+0xca/0x240 mm/kasan/report.c:482
 kasan_report+0x118/0x150 mm/kasan/report.c:595
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200
 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
 ext4_read_inline_data+0x18f/0x280 fs/ext4/inline.c:214
 ext4_read_inline_dir+0x2cd/0x940 fs/ext4/inline.c:1395
 ext4_readdir+0x252/0x2d10 fs/ext4/dir.c:162
 iterate_dir+0x1a7/0x4c0 fs/readdir.c:108
 __do_sys_getdents64 fs/readdir.c:410 [inline]
 __se_sys_getdents64+0xd3/0x1b0 fs/readdir.c:396
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x8f/0x250 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff07a549333
Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 02 45 f8 ff 66 90 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 c7 c2 a8 ff ff ff f7 d8
RSP: 002b:00007ffd4a34ee78 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 000055555565c520 RCX: 00007ff07a549333
RDX: 0000000000008000 RSI: 000055555565c520 RDI: 0000000000000006
RBP: 000055555565c4f4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffa8
R13: 0000000000000016 R14: 000055555565c4f0 R15: 00007ffd4a352210
 </TASK>

Allocated by task 2391:
 kasan_save_stack mm/kasan/common.c:56 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:77
 unpoison_slab_object mm/kasan/common.c:342 [inline]
 __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:368
 kasan_slab_alloc include/linux/kasan.h:252 [inline]
 slab_post_alloc_hook mm/slub.c:4947 [inline]
 slab_alloc_node mm/slub.c:5246 [inline]
 kmem_cache_alloc_noprof+0x315/0x620 mm/slub.c:5253
 getname_flags+0x9b/0x490 fs/namei.c:146
 user_path_at+0x1c/0x50 fs/namei.c:3214
 do_faccessat+0x491/0x9f0 fs/open.c:493
 __do_sys_access fs/open.c:552 [inline]
 __se_sys_access fs/open.c:550 [inline]
 __x64_sys_access+0x5c/0x70 fs/open.c:550
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x8f/0x250 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 2391:
 kasan_save_stack mm/kasan/common.c:56 [inline]
 kasan_save_track+0x3e/0x80 mm/kasan/common.c:77
 __kasan_save_free_info+0x46/0x50 mm/kasan/generic.c:587
 kasan_save_free_info mm/kasan/kasan.h:406 [inline]
 poison_slab_object mm/kasan/common.c:252 [inline]
 __kasan_slab_free+0x5c/0x80 mm/kasan/common.c:284
 kasan_slab_free include/linux/kasan.h:234 [inline]
 slab_free_hook mm/slub.c:2515 [inline]
 slab_free mm/slub.c:6574 [inline]
 kmem_cache_free+0x186/0x610 mm/slub.c:6684
 user_path_at+0x3c/0x50 fs/namei.c:3217
 do_faccessat+0x491/0x9f0 fs/open.c:493
 __do_sys_access fs/open.c:552 [inline]
 __se_sys_access fs/open.c:550 [inline]
 __x64_sys_access+0x5c/0x70 fs/open.c:550
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x8f/0x250 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The buggy address belongs to the object at ffff88811c30a200
 which belongs to the cache names_cache of size 4096
The buggy address is located 794 bytes inside of
 freed 4096-byte region [ffff88811c30a200, ffff88811c30b200)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11c308
head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0
flags: 0x200000000000040(head|node=0|zone=2)
page_type: f5(slab)
raw: 0200000000000040 ffff888100ec7640 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000070007 00000000f5000000 0000000000000000
head: 0200000000000040 ffff888100ec7640 dead000000000122 0000000000000000
head: 0000000000000000 0000000000070007 00000000f5000000 0000000000000000
head: 0200000000000003 ffffea000470c201 00000000ffffffff 00000000ffffffff
head: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000008
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 2391, tgid 2391 (kworker/u8:9), ts 76772096618, free_ts 70008360403
 set_page_owner include/linux/page_owner.h:32 [inline]
 post_alloc_hook+0x168/0x1a0 mm/page_alloc.c:1850
 prep_new_page mm/page_alloc.c:1858 [inline]
 get_page_from_freelist+0x29f0/0x2bb0 mm/page_alloc.c:3884
 __alloc_frozen_pages_noprof+0x26b/0x460 mm/page_alloc.c:5183
 alloc_pages_mpol+0xcb/0x270 mm/mempolicy.c:2416
 alloc_slab_page mm/slub.c:3031 [inline]
 allocate_slab+0x96/0x350 mm/slub.c:3204
 new_slab mm/slub.c:3258 [inline]
 ___slab_alloc+0xb41/0x1330 mm/slub.c:4628
 __slab_alloc+0x54/0xc0 mm/slub.c:4747
 __slab_alloc_node mm/slub.c:4823 [inline]
 slab_alloc_node mm/slub.c:5234 [inline]
 kmem_cache_alloc_noprof+0x3ab/0x620 mm/slub.c:5253
 getname_kernel+0x51/0x2a0 fs/namei.c:249
 kern_path+0x12/0x40 fs/namei.c:2862
 tomoyo_realpath_nofollow+0x8a/0xe0 security/tomoyo/realpath.c:303
 tomoyo_find_next_domain+0x260/0x1a40 security/tomoyo/domain.c:730
 tomoyo_bprm_check_security+0x101/0x140 security/tomoyo/tomoyo.c:102
 security_bprm_check+0x2b/0xb0 security/security.c:1341
 search_binary_handler fs/exec.c:1660 [inline]
 exec_binprm fs/exec.c:1702 [inline]
 bprm_execve+0x610/0xe80 fs/exec.c:1754
 kernel_execve+0x4d3/0x5f0 fs/exec.c:1920
page last free pid 1884 tgid 1884 stack trace:
 reset_page_owner include/linux/page_owner.h:25 [inline]
 free_pages_prepare mm/page_alloc.c:1394 [inline]
 __free_frozen_pages+0xa62/0xbd0 mm/page_alloc.c:2906
 __folio_put+0x1b9/0x240 mm/swap.c:112
 put_netmem net/core/skbuff.c:7375 [inline]
 skb_page_unref include/linux/skbuff_ref.h:43 [inline]
 __skb_frag_unref include/linux/skbuff_ref.h:56 [inline]
 skb_release_data+0x3a2/0x600 net/core/skbuff.c:1081
 skb_release_all net/core/skbuff.c:1152 [inline]
 __kfree_skb+0x48/0x50 net/core/skbuff.c:1166
 tcp_clean_rtx_queue net/ipv4/tcp_input.c:3471 [inline]
 tcp_ack+0x1272/0x55c0 net/ipv4/tcp_input.c:4096
 tcp_rcv_established+0x11f1/0x2630 net/ipv4/tcp_input.c:6341
 tcp_v4_do_rcv+0x239/0xab0 net/ipv4/tcp_ipv4.c:1931
 __release_sock+0xf3/0x1a0 net/core/sock.c:3180
 __sk_flush_backlog+0x31/0xa0 net/core/sock.c:3203
 sk_flush_backlog include/net/sock.h:1221 [inline]
 tcp_sendmsg_locked+0x3428/0x4510 net/ipv4/tcp.c:1214
 tcp_sendmsg+0x27/0x40 net/ipv4/tcp.c:1413
 sock_sendmsg_nosec net/socket.c:727 [inline]
 __sock_sendmsg+0x163/0x220 net/socket.c:742
 sock_write_iter+0x1f5/0x2f0 net/socket.c:1195
 new_sync_write fs/read_write.c:593 [inline]
 vfs_write+0x568/0xc70 fs/read_write.c:686
 ksys_write+0x108/0x1f0 fs/read_write.c:738
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x8f/0x250 arch/x86/entry/syscall_64.c:94

Memory state around the buggy address:
 ffff88811c30a400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88811c30a480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff88811c30a500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
                            ^
 ffff88811c30a580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88811c30a600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================