syzbot


BUG: sleeping function called from invalid context in exit_mmap

Status: auto-obsoleted due to no activity on 2024/10/07 04:42
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+3d69736e9e836dd043cf@syzkaller.appspotmail.com
First crash: 273d, last: 273d
Bug presence (2)
Date Name Commit Repro Result
2024/02/21 linux-5.15.y (ToT) 6139f2a02fe0 C [report] BUG: sleeping function called from invalid context in task_work_run
2024/02/21 upstream (ToT) 39133352cbed 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 exit_mmap origin:lts-only C unreliable 3 276d 284d 0/3 upstream: reported C repro on 2024/02/10 19:16
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/07 03:36 1h04m retest repro linux-5.15.y OK log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/03/12 23:03 5h39m fix candidate upstream OK (1) job log

Sample crash report:
BUG: sleeping function called from invalid context at mm/mmap.c:3198
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5543, name: syz-executor409
no locks held by syz-executor409/5543.
Preemption disabled at:
[<ffffffff8174f806>] is_module_text_address+0x16/0x140 kernel/module.c:4758
CPU: 0 PID: 5543 Comm: syz-executor409 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
 exit_mmap+0x569/0x670 mm/mmap.c:3198
 __mmput+0x112/0x3b0 kernel/fork.c:1126
 exit_mm+0x688/0x7f0 kernel/exit.c:548
 do_exit+0x626/0x2480 kernel/exit.c:859
 do_group_exit+0x144/0x310 kernel/exit.c:994
 __do_sys_exit_group kernel/exit.c:1005 [inline]
 __se_sys_exit_group kernel/exit.c:1003 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
 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:0x7f56e88f25b9
Code: Unable to access opcode bytes at RIP 0x7f56e88f258f.
RSP: 002b:00007ffed75d9e28 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f56e88f25b9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f56e896e370 R08: ffffffffffffffb8 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f56e896e370
R13: 0000000000000000 R14: 00007f56e896ede0 R15: 00007f56e88c3500
 </TASK>
BUG: scheduling while atomic: syz-executor409/5543/0x00000002
no locks held by syz-executor409/5543.
Modules linked in:
Preemption disabled at:
[<ffffffff8174f806>] is_module_text_address+0x16/0x140 kernel/module.c:4758

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/21 15:33 linux-5.15.y 6139f2a02fe0 3af7dd65 .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 exit_mmap
* Struck through repros no longer work on HEAD.