syzbot


BUG: sleeping function called from invalid context in __vunmap

Status: auto-obsoleted due to no activity on 2024/10/04 07:20
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+6dd38ad504982f1e65ab@syzkaller.appspotmail.com
First crash: 303d, last: 303d
Bug presence (2)
Date Name Commit Repro Result
2024/02/09 linux-5.15.y (ToT) 6139f2a02fe0 C [report] BUG: sleeping function called from invalid context in exit_mmap
2024/02/09 upstream (ToT) 1f719a2f3fa6 C Didn't crash
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 BUG: sleeping function called from invalid context in __vunmap origin:lts-only C done 2 291d 294d 0/3 upstream: reported C repro on 2024/02/18 12:21
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/04 06:11 1h08m retest repro linux-5.15.y OK log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/02/20 23:07 6h21m fix candidate upstream OK (1) job log

Sample crash report:
BUG: sleeping function called from invalid context at mm/vmalloc.c:2622
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 4138, name: syz-executor200
no locks held by syz-executor200/4138.
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 4138 Comm: syz-executor200 Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 ___might_sleep+0x547/0x6a0 kernel/sched/core.c:9626
 __vunmap+0x8e7/0xa20 mm/vmalloc.c:2622
 bpf_check+0x6cb6/0x12d00 kernel/bpf/verifier.c:14179
 bpf_prog_load+0x12b3/0x1b60 kernel/bpf/syscall.c:2325
 __sys_bpf+0x343/0x670 kernel/bpf/syscall.c:4623
 __do_sys_bpf kernel/bpf/syscall.c:4727 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4725 [inline]
 __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4725
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f49fb1ea659
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe7136f2e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 000000000000eed9 RCX: 00007f49fb1ea659
RDX: 0000000000000049 RSI: 0000000020000980 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe7136f30c
R13: 00007ffe7136f340 R14: 00007ffe7136f320 R15: 0000000000000000
 </TASK>
BUG: scheduling while atomic: syz-executor200/4138/0x00000002
no locks held by syz-executor200/4138.
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/09 08:10 linux-5.15.y 6139f2a02fe0 7f07e9b0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: sleeping function called from invalid context in __vunmap
* Struck through repros no longer work on HEAD.