syzbot


BUG: scheduling while atomic in _vm_unmap_aliases

Status: upstream: reported C repro on 2024/03/13 09:20
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+565abaf53d73a9910bff@syzkaller.appspotmail.com
First crash: 45d, last: 7d11h
Bug presence (2)
Date Name Commit Repro Result
2024/03/13 lts (merge base) 6139f2a02fe0 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/04/10 upstream (ToT) 2c71fdf02a95 C Didn't crash

Sample crash report:
BUG: scheduling while atomic: syz-executor330/327/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165eb4a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 1 PID: 327 Comm: syz-executor330 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #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/0x17 lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5707
 schedule_debug kernel/sched/core.c:5734 [inline]
 __schedule+0xd19/0x1590 kernel/sched/core.c:6402
 schedule+0x11f/0x1e0 kernel/sched/core.c:6595
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6654
 mutex_optimistic_spin kernel/locking/mutex.c:521 [inline]
 __mutex_lock_common kernel/locking/mutex.c:620 [inline]
 __mutex_lock+0x5b5/0x1870 kernel/locking/mutex.c:755
 __mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1006
 mutex_lock+0x135/0x1e0 kernel/locking/mutex.c:288
 _vm_unmap_aliases+0x328/0x3b0 mm/vmalloc.c:2116
 vm_unmap_aliases+0x19/0x20 mm/vmalloc.c:2141
 change_page_attr_set_clr+0x308/0x1050 arch/x86/mm/pat/set_memory.c:1740
 change_page_attr_clear arch/x86/mm/pat/set_memory.c:1797 [inline]
 set_memory_ro+0xa1/0xe0 arch/x86/mm/pat/set_memory.c:1943
 bpf_jit_binary_lock_ro include/linux/filter.h:888 [inline]
 bpf_int_jit_compile+0xbf42/0xc6d0 arch/x86/net/bpf_jit_comp.c:2372
 bpf_prog_select_runtime+0x706/0x9e0 kernel/bpf/core.c:1930
 bpf_prog_load+0x1315/0x1b50 kernel/bpf/syscall.c:2331
 __sys_bpf+0x4bc/0x760 kernel/bpf/syscall.c:4627
 __do_sys_bpf kernel/bpf/syscall.c:4731 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:4729 [inline]
 __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:4729
 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:0x7fa35a3d2029
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 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:00007ffe40f3de38 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa35a3d2029
RDX: 0000000000000090 RSI: 00000000200004c0 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/20 09:12 android13-5.15-lts ad06eaf051cd af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/08 01:38 android13-5.15-lts 993bed180178 ca620dd8 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/07 09:30 android13-5.15-lts 993bed180178 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/06 12:02 android13-5.15-lts 993bed180178 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/03 14:29 android13-5.15-lts 993bed180178 7925100d .config strace log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/03 12:43 android13-5.15-lts 993bed180178 7925100d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/03/13 09:11 android13-5.15-lts 993bed180178 db5b7ff0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/16 20:12 android13-5.15-lts ad06eaf051cd 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/10 22:55 android13-5.15-lts 993bed180178 4320ec32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/04/08 14:40 android13-5.15-lts 993bed180178 53df08b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/03/23 15:27 android13-5.15-lts 993bed180178 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
2024/03/13 05:54 android13-5.15-lts 993bed180178 db5b7ff0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in _vm_unmap_aliases
* Struck through repros no longer work on HEAD.