syzbot


BUG: scheduling while atomic in __put_anon_vma

Status: upstream: reported C repro on 2024/04/21 22:35
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+a4a5ffb3aa135ac51bc1@syzkaller.appspotmail.com
First crash: 63d, last: 29d
Bug presence (2)
Date Name Commit Repro Result
2024/04/21 lts (merge base) 883d1a956208 C [report] BUG: scheduling while atomic in do_task_dead
2024/04/21 upstream (ToT) ed30a4a51bb1 C Didn't crash
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/05/06 00:02 13m retest repro android14-6.1 report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/05/26 02:16 1h07m bisect fix android14-6.1 job log (0) log

Sample crash report:
BUG: scheduling while atomic: syz-executor384/790/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8163d87f>] is_module_text_address+0x1f/0x360 kernel/module/main.c:3140
CPU: 1 PID: 790 Comm: syz-executor384 Not tainted 6.1.75-syzkaller-00037-gdcb09569bbff #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 dump_stack+0x15/0x1b lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5960
 schedule_debug kernel/sched/core.c:5987 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6622
 schedule+0xc3/0x180 kernel/sched/core.c:6805
 rwsem_down_write_slowpath+0xddf/0x20a0 kernel/locking/rwsem.c:1227
 __down_write_common kernel/locking/rwsem.c:1357 [inline]
 __down_write kernel/locking/rwsem.c:1366 [inline]
 down_write+0x21/0x30 kernel/locking/rwsem.c:1619
 anon_vma_lock_write include/linux/rmap.h:121 [inline]
 anon_vma_free mm/rmap.c:135 [inline]
 __put_anon_vma+0x93/0x1d0 mm/rmap.c:2376
 put_anon_vma include/linux/rmap.h:116 [inline]
 unlink_anon_vmas+0x468/0x5b0 mm/rmap.c:446
 free_pgtables+0x30a/0x660 mm/memory.c:423
 exit_mmap+0x415/0x940 mm/mmap.c:3341
 __mmput+0x95/0x310 kernel/fork.c:1298
 mmput+0x56/0x170 kernel/fork.c:1321
 exit_mm kernel/exit.c:566 [inline]
 do_exit+0xb29/0x2b80 kernel/exit.c:862
 do_group_exit+0x21a/0x2d0 kernel/exit.c:1025
 get_signal+0x169d/0x1820 kernel/signal.c:2880
 arch_do_signal_or_restart+0xb0/0x16f0 arch/x86/kernel/signal.c:871
 exit_to_user_mode_loop+0x74/0xa0 kernel/entry/common.c:168
 exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
 irqentry_exit_to_user_mode+0x9/0x20 kernel/entry/common.c:310
 irqentry_exit+0x12/0x40 kernel/entry/common.c:413
 exc_page_fault+0x4f3/0x700 arch/x86/mm/fault.c:1565
 asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x7fa82e7cfaa1
Code: Unable to access opcode bytes at 0x7fa82e7cfa77.
RSP: 002b:0000000000000040 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007fa82e85a348 RCX: 00007fa82e7cfa99
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: 00007fa82e85a340 R08: 0000000000000000 R09: 00007fa82e7906c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fa82e827074
R13: 0000000000000000 R14: 00007ffe30883b20 R15: 00007ffe30883c08
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/21 22:34 android14-6.1 dcb09569bbff af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-6-1 BUG: scheduling while atomic in __put_anon_vma
* Struck through repros no longer work on HEAD.