loop4: rw=2049, sector=40, nr_sectors = 4 limit=40
Buffer I/O error on dev loop4, logical block 10, lost async page write
loop3: detected capacity change from 0 to 40
==================================================================
BUG: KASAN: use-after-free in __lock_acquire+0x42c9/0x5e70
Read of size 8 at addr ffff88800d9ae1c8 by task kmemleak/54

CPU: 0 PID: 54 Comm: kmemleak Not tainted 5.19.0-rc7-next-20220718 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x8b/0xb3
 print_report.cold+0x5e/0x5e5
 kasan_report+0xb1/0x1c0
 __lock_acquire+0x42c9/0x5e70
 lock_acquire+0x1a2/0x530
 _raw_spin_lock_irq+0x32/0x50
 kmemleak_scan+0x21d/0x16f0
 kmemleak_scan_thread+0x8f/0xb1
 kthread+0x2ed/0x3a0
 ret_from_fork+0x22/0x30
 </TASK>

Allocated by task 9601:
 kasan_save_stack+0x1e/0x40
 __kasan_slab_alloc+0x66/0x80
 kmem_cache_alloc+0x1b1/0x4a0
 __create_object.isra.0+0x3d/0xc10
 __kmalloc_node+0x278/0x480
 kvmalloc_node+0x41/0x1e0
 simple_xattr_alloc+0x43/0xa0
 simple_xattr_set+0x75/0x610
 __vfs_setxattr+0x115/0x180
 __vfs_setxattr_noperm+0x125/0x600
 __vfs_setxattr_locked+0x1d3/0x260
 vfs_setxattr+0x110/0x3c0
 setxattr+0x14d/0x170
 path_setxattr+0x19b/0x1d0
 __x64_sys_setxattr+0xc0/0x160
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Freed by task 9617:
 kasan_save_stack+0x1e/0x40
 kasan_set_track+0x21/0x30
 kasan_set_free_info+0x20/0x40
 __kasan_slab_free+0x108/0x190
 kmem_cache_free+0xfb/0x610
 rcu_core+0x7e2/0x2080
 __do_softirq+0x1c8/0x8d0

Last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x97/0xb0
 call_rcu+0x6a/0xa30
 kfree+0xbb/0x5e0
 kvfree+0x42/0x50
 simple_xattr_set+0x3f8/0x610
 __vfs_setxattr+0x115/0x180
 __vfs_setxattr_noperm+0x125/0x600
 __vfs_setxattr_locked+0x1d3/0x260
 vfs_setxattr+0x110/0x3c0
 setxattr+0x14d/0x170
 path_setxattr+0x19b/0x1d0
 __x64_sys_setxattr+0xc0/0x160
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Second to last potentially related work creation:
 kasan_save_stack+0x1e/0x40
 __kasan_record_aux_stack+0x97/0xb0
 call_rcu+0x6a/0xa30
 kmem_cache_free+0xc1/0x610
 unlink_anon_vmas+0x3d0/0x6f0
 free_pgtables+0x24d/0x420
 exit_mmap+0x1b4/0x680
 mmput+0xd1/0x390
 do_exit+0x9e0/0x27a0
 do_group_exit+0xd2/0x2f0
 __x64_sys_exit_group+0x3a/0x50
 do_syscall_64+0x3b/0x90
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The buggy address belongs to the object at ffff88800d9ae1b0
 which belongs to the cache kmemleak_object of size 368
The buggy address is located 24 bytes inside of
 368-byte region [ffff88800d9ae1b0, ffff88800d9ae320)

The buggy address belongs to the physical page:
page:00000000326a130e refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xd9ae
head:00000000326a130e order:1 compound_mapcount:0 compound_pincount:0
flags: 0x100000000010200(slab|head|node=0|zone=1)
raw: 0100000000010200 ffffea0000231000 dead000000000004 ffff888007c4f780
raw: 0000000000000000 0000000000120012 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff88800d9ae080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88800d9ae100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fc fc
>ffff88800d9ae180: fc fc fc fc fc fc fa fb fb fb fb fb fb fb fb fb
                                              ^
 ffff88800d9ae200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ffff88800d9ae280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================