syzbot


BUG: sleeping function called from invalid context in exit_mmap

Status: upstream: reported C repro on 2024/02/10 19:16
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+d4537ef54c2cacf80745@syzkaller.appspotmail.com
First crash: 285d, last: 276d
Bug presence (2)
Date Name Commit Repro Result
2024/02/10 linux-6.1.y (ToT) f1bb70486c9c C [report] INFO: rcu detected stall in corrupted
2024/02/10 upstream (ToT) a5b6244cf87c C Didn't crash
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 BUG: sleeping function called from invalid context in exit_mmap origin:lts-only C unreliable 1 274d 274d 0/3 auto-obsoleted due to no activity on 2024/10/07 04:42
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/02/13 20:57 7h12m fix candidate upstream OK (1) job log

Sample crash report:
BUG: sleeping function called from invalid context at mm/mmap.c:3251
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 4507, name: syz-executor224
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
1 lock held by syz-executor224/4507:
 #0: ffff88801fac26d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
 #0: ffff88801fac26d8 (&mm->mmap_lock){++++}-{3:3}, at: exit_mmap+0x29a/0x9f0 mm/mmap.c:3235
Preemption disabled at:
[<ffffffff817677fa>] is_module_text_address+0x1a/0x160 kernel/module/main.c:3097
CPU: 1 PID: 4507 Comm: syz-executor224 Not tainted 6.1.78-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_resched+0x5cb/0x780 kernel/sched/core.c:9942
 exit_mmap+0x54b/0x9f0 mm/mmap.c:3251
 __mmput+0x115/0x3c0 kernel/fork.c:1199
 exit_mm+0x226/0x300 kernel/exit.c:563
 do_exit+0x9f6/0x26a0 kernel/exit.c:856
 do_group_exit+0x202/0x2b0 kernel/exit.c:1019
 __do_sys_exit_group kernel/exit.c:1030 [inline]
 __se_sys_exit_group kernel/exit.c:1028 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f67f1a8d539
Code: Unable to access opcode bytes at 0x7f67f1a8d50f.
RSP: 002b:00007fffe71c5f18 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f67f1a8d539
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f67f1b0e2d0 R08: ffffffffffffffb8 R09: 0000555556c55610
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f67f1b0e2d0
R13: 0000000000000000 R14: 00007f67f1b0fda0 R15: 00007f67f1a5e6d0
 </TASK>
BUG: scheduling while atomic: syz-executor224/4507/0x00000002
no locks held by syz-executor224/4507.
Modules linked in:
Preemption disabled at:
[<ffffffff817677fa>] is_module_text_address+0x1a/0x160 kernel/module/main.c:3097

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/19 00:08 linux-6.1.y 8b4118fabd6e 578f7538 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf BUG: sleeping function called from invalid context in exit_mmap
2024/02/12 09:38 linux-6.1.y f1bb70486c9c 77b23aa1 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf BUG: sleeping function called from invalid context in exit_mmap
2024/02/10 19:15 linux-6.1.y f1bb70486c9c 77b23aa1 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-perf BUG: sleeping function called from invalid context in exit_mmap
* Struck through repros no longer work on HEAD.