Hello,
syzbot found the following issue on:
HEAD commit: 24be4d0b46bb arch/arm64/mm/fault: Fix undeclared variable ..
git tree: upstream
console output:
https://syzkaller.appspot.com/x/log.txt?x=12c7fe94a80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=509b1402bb10d257
dashboard link:
https://syzkaller.appspot.com/bug?extid=c370a63abf53498ae3e2
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [
c...@fb.com dst...@suse.com jo...@toxicpanda.com linux...@vger.kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/fd71e9206169/disk-24be4d0b.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/f1d31fd4f48d/vmlinux-24be4d0b.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/3741344138ae/bzImage-24be4d0b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+c370a6...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-use-after-free in xa_head include/linux/xarray.h:1182 [inline]
BUG: KASAN: slab-use-after-free in xas_start+0x1ef/0x7b0 lib/xarray.c:190
Read of size 8 at addr ffff888077ec2bf8 by task syz-executor.0/6659
CPU: 0 PID: 6659 Comm: syz-executor.0 Not tainted 6.4.0-syzkaller-11311-g24be4d0b46bb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0x163/0x540 mm/kasan/report.c:475
kasan_report+0x175/0x1b0 mm/kasan/report.c:588
xa_head include/linux/xarray.h:1182 [inline]
xas_start+0x1ef/0x7b0 lib/xarray.c:190
xas_load lib/xarray.c:237 [inline]
xas_find+0x177/0xaa0 lib/xarray.c:1250
find_get_entry mm/filemap.c:1973 [inline]
find_lock_entries+0x265/0x10f0 mm/filemap.c:2074
truncate_inode_pages_range+0x202/0x11b0 mm/truncate.c:364
evict_inode_truncate_pages fs/btrfs/inode.c:5221 [inline]
btrfs_evict_inode+0x208/0x1000 fs/btrfs/inode.c:5344
evict+0x2a4/0x620 fs/inode.c:665
dispose_list fs/inode.c:698 [inline]
evict_inodes+0x5f8/0x690 fs/inode.c:748
generic_shutdown_super+0x98/0x340 fs/super.c:478
kill_anon_super+0x3b/0x60 fs/super.c:1110
btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2138
deactivate_locked_super+0xa4/0x110 fs/super.c:330
cleanup_mnt+0x426/0x4c0 fs/namespace.c:1254
task_work_run+0x24a/0x300 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x64/0x280 kernel/entry/common.c:297
do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f5d2bc8d7f7
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 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:00007fff8a845338 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f5d2bc8d7f7
RDX: 00007fff8a84540b RSI: 000000000000000a RDI: 00007fff8a845400
RBP: 00007fff8a845400 R08: 00000000ffffffff R09: 00007fff8a8451d0
R10: 00005555568e0893 R11: 0000000000000246 R12: 00007f5d2bcd643b
R13: 00007fff8a8464c0 R14: 00005555568e0810 R15: 00007fff8a846500
</TASK>
Allocated by task 14764:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4f/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x66/0x70 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:186 [inline]
slab_post_alloc_hook+0x68/0x3a0 mm/slab.h:750
slab_alloc_node mm/slub.c:3470 [inline]
slab_alloc mm/slub.c:3478 [inline]
__kmem_cache_alloc_lru mm/slub.c:3485 [inline]
kmem_cache_alloc_lru+0x122/0x300 mm/slub.c:3501
alloc_inode_sb include/linux/fs.h:2729 [inline]
btrfs_alloc_inode+0x58/0x3c0 fs/btrfs/inode.c:8552
alloc_inode fs/inode.c:260 [inline]
new_inode_pseudo+0x65/0x1d0 fs/inode.c:1018
new_inode+0x29/0x1d0 fs/inode.c:1046
btrfs_create+0x4b/0x140 fs/btrfs/inode.c:6639
lookup_open fs/namei.c:3492 [inline]
open_last_lookups fs/namei.c:3560 [inline]
path_openat+0x13e7/0x3180 fs/namei.c:3790
do_filp_open+0x234/0x490 fs/namei.c:3820
do_sys_openat2+0x13e/0x1d0 fs/open.c:1407
do_sys_open fs/open.c:1422 [inline]
__do_sys_open fs/open.c:1430 [inline]
__se_sys_open fs/open.c:1426 [inline]
__x64_sys_open+0x225/0x270 fs/open.c:1426
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Freed by task 14828:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4f/0x70 mm/kasan/common.c:52
kasan_save_free_info+0x28/0x40 mm/kasan/generic.c:521
____kasan_slab_free+0xd6/0x120 mm/kasan/common.c:236
kasan_slab_free include/linux/kasan.h:162 [inline]
slab_free_hook mm/slub.c:1792 [inline]
slab_free_freelist_hook mm/slub.c:1818 [inline]
slab_free mm/slub.c:3801 [inline]
kmem_cache_free+0x292/0x500 mm/slub.c:3823
rcu_do_batch kernel/rcu/tree.c:2135 [inline]
rcu_core+0xaaa/0x1740 kernel/rcu/tree.c:2399
__do_softirq+0x2ab/0x908 kernel/softirq.c:553
Last potentially related work creation:
kasan_save_stack+0x3f/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xad/0xc0 mm/kasan/generic.c:491
__call_rcu_common kernel/rcu/tree.c:2649 [inline]
call_rcu+0x167/0xa70 kernel/rcu/tree.c:2763
__btrfs_run_defrag_inode fs/btrfs/defrag.c:282 [inline]
btrfs_run_defrag_inodes+0xa90/0xe20 fs/btrfs/defrag.c:328
cleaner_kthread+0x287/0x3c0 fs/btrfs/disk-io.c:1487
kthread+0x2b8/0x350 kernel/kthread.c:389
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
The buggy address belongs to the object at ffff888077ec2540
which belongs to the cache btrfs_inode of size 2256
The buggy address is located 1720 bytes inside of
freed 2256-byte region [ffff888077ec2540, ffff888077ec2e10)
The buggy address belongs to the physical page:
page:ffffea0001dfb000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x77ec0
head:ffffea0001dfb000 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff8880517d3a01
flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000010200 ffff88814c12b780 dead000000000122 0000000000000000
raw: 0000000000000000 00000000000d000d 00000001ffffffff ffff8880517d3a01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d20d0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 14755, tgid 14755 (btrfs-cleaner), ts 647294567602, free_ts 618754245154
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1e6/0x210 mm/page_alloc.c:1570
prep_new_page mm/page_alloc.c:1577 [inline]
get_page_from_freelist+0x31e8/0x3370 mm/page_alloc.c:3221
__alloc_pages+0x255/0x670 mm/page_alloc.c:4477
alloc_slab_page+0x6a/0x160 mm/slub.c:1862
allocate_slab mm/slub.c:2009 [inline]
new_slab+0x84/0x2f0 mm/slub.c:2062
___slab_alloc+0xade/0x1100 mm/slub.c:3215
__slab_alloc mm/slub.c:3314 [inline]
__slab_alloc_node mm/slub.c:3367 [inline]
slab_alloc_node mm/slub.c:3460 [inline]
slab_alloc mm/slub.c:3478 [inline]
__kmem_cache_alloc_lru mm/slub.c:3485 [inline]
kmem_cache_alloc_lru+0x1bf/0x300 mm/slub.c:3501
alloc_inode_sb include/linux/fs.h:2729 [inline]
btrfs_alloc_inode+0x58/0x3c0 fs/btrfs/inode.c:8552
alloc_inode fs/inode.c:260 [inline]
iget5_locked+0xa0/0x270 fs/inode.c:1283
btrfs_iget_locked fs/btrfs/inode.c:5668 [inline]
btrfs_iget_path+0x149/0x1520 fs/btrfs/inode.c:5685
__btrfs_run_defrag_inode fs/btrfs/defrag.c:259 [inline]
btrfs_run_defrag_inodes+0x6bd/0xe20 fs/btrfs/defrag.c:328
cleaner_kthread+0x287/0x3c0 fs/btrfs/disk-io.c:1487
kthread+0x2b8/0x350 kernel/kthread.c:389
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1161 [inline]
free_unref_page_prepare+0x903/0xa30 mm/page_alloc.c:2348
free_unref_page+0x37/0x3f0 mm/page_alloc.c:2443
__slab_free+0x2f6/0x390 mm/slub.c:3707
qlist_free_all+0x22/0x60 mm/kasan/quarantine.c:185
kasan_quarantine_reduce+0x14b/0x160 mm/kasan/quarantine.c:292
__kasan_slab_alloc+0x23/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:186 [inline]
slab_post_alloc_hook+0x68/0x3a0 mm/slab.h:750
slab_alloc_node mm/slub.c:3470 [inline]
slab_alloc mm/slub.c:3478 [inline]
__kmem_cache_alloc_lru mm/slub.c:3485 [inline]
kmem_cache_alloc+0x123/0x300 mm/slub.c:3494
f2fs_kmem_cache_alloc_nofail fs/f2fs/f2fs.h:2759 [inline]
f2fs_kmem_cache_alloc fs/f2fs/f2fs.h:2769 [inline]
add_free_nid+0xdc/0x700 fs/f2fs/node.c:2289
scan_free_nid_bits fs/f2fs/node.c:2440 [inline]
__f2fs_build_free_nids fs/f2fs/node.c:2474 [inline]
f2fs_build_free_nids+0x514/0x11a0 fs/f2fs/node.c:2532
f2fs_balance_fs_bg+0x167/0x990 fs/f2fs/segment.c:481
f2fs_write_node_pages+0x146/0x6a0 fs/f2fs/node.c:2110
do_writepages+0x3a6/0x670 mm/page-writeback.c:2551
__writeback_single_inode+0x155/0xfa0 fs/fs-writeback.c:1603
writeback_sb_inodes+0x8e3/0x11d0 fs/fs-writeback.c:1894
wb_writeback+0x44d/0xc60 fs/fs-writeback.c:2070
Memory state around the buggy address:
ffff888077ec2a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888077ec2b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
>ffff888077ec2b80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888077ec2c00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888077ec2c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup