syzbot
WARNING: lock held when returning to user space in query_matching_vma
Status:
auto-obsoleted due to no activity on 2025/10/23 00:21
Subsystems:
fs
[Documentation on labels]
Reported-by: syzbot+add57955be940be754a1@syzkaller.appspotmail.com
First crash: 395d, last: 393d
▶
▼
Last patch testing requests (4)
Sample crash report:
================================================
WARNING: lock held when returning to user space!
6.16.0-rc6-next-20250714-syzkaller #0 Not tainted
------------------------------------------------
syz.2.456/7303 is leaving the kernel with locks still held!
4 locks held by syz.2.456/7303:
#0: ffff888074053948 (vm_lock){++++}-{0:0}, at: get_next_vma fs/proc/task_mmu.c:182 [inline]
#0: ffff888074053948 (vm_lock){++++}-{0:0}, at: query_vma_find_by_addr fs/proc/task_mmu.c:512 [inline]
#0: ffff888074053948 (vm_lock){++++}-{0:0}, at: query_matching_vma+0x319/0x5c0 fs/proc/task_mmu.c:544
#1: ffff888074053a88 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220
#2: ffff888074053bc8 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220
#3: ffff888074053d08 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220
* Struck through repros no longer work on HEAD.