syzbot


WARNING: suspicious RCU usage in unmap_page_range

Status: auto-closed as invalid on 2021/09/14 19:32
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+4ca458af025542e76123@syzkaller.appspotmail.com
First crash: 1255d, last: 1068d
Discussions (1)
Title Replies (including bot) Last reply
WARNING: suspicious RCU usage in unmap_page_range 0 (1) 2020/11/15 19:30

Sample crash report:
=============================
WARNING: suspicious RCU usage
5.13.0-rc2-syzkaller #0 Not tainted
-----------------------------
kernel/sched/core.c:8304 Illegal context switch in RCU-bh read-side critical section!

other info that might help us debug this:


rcu_scheduler_active = 2, debug_locks = 0
no locks held by syz-executor.2/13976.

stack backtrace:
CPU: 1 PID: 13976 Comm: syz-executor.2 Not tainted 5.13.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:79 [inline]
 dump_stack+0x141/0x1d7 lib/dump_stack.c:120
 ___might_sleep+0x229/0x2c0 kernel/sched/core.c:8304
 zap_pmd_range mm/memory.c:1376 [inline]
 zap_pud_range mm/memory.c:1403 [inline]
 zap_p4d_range mm/memory.c:1424 [inline]
 unmap_page_range+0x1722/0x2650 mm/memory.c:1445
 unmap_single_vma+0x198/0x300 mm/memory.c:1490
 unmap_vmas+0x16d/0x2f0 mm/memory.c:1522
 exit_mmap+0x2a8/0x590 mm/mmap.c:3208
 __mmput+0x122/0x470 kernel/fork.c:1096
 mmput+0x58/0x60 kernel/fork.c:1117
 exit_mm kernel/exit.c:502 [inline]
 do_exit+0xb0a/0x2a60 kernel/exit.c:813
 do_group_exit+0x125/0x310 kernel/exit.c:923
 get_signal+0x47f/0x2150 kernel/signal.c:2818
 arch_do_signal_or_restart+0x2a8/0x1eb0 arch/x86/kernel/signal.c:789
 handle_signal_work kernel/entry/common.c:147 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:171 [inline]
 exit_to_user_mode_prepare+0x171/0x280 kernel/entry/common.c:208
 __syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
 syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:301
 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:57
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x4665d9
Code: Unable to access opcode bytes at RIP 0x4665af.
RSP: 002b:00007f4b5404a218 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 000000000056c010 RCX: 00000000004665d9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 000000000056c014
RBP: 000000000056c008 R08: 0000000000000009 R09: 0000000000000000
R10: ffffffffffffffff R11: 0000000000000246 R12: 000000000056c014
R13: 00007ffc71f94e5f R14: 00007f4b5404a300 R15: 0000000000022000

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/05/17 19:32 upstream d07f6ca923ea a2eb125d .config console log report info ci-upstream-kasan-gce-selinux-root WARNING: suspicious RCU usage in unmap_page_range
2021/04/02 01:55 upstream ffd9fb546d49 6a81331a .config console log report info ci-upstream-kasan-gce-selinux-root WARNING: suspicious RCU usage in unmap_page_range
2021/03/31 17:30 upstream 5e46d1b78a03 6a81331a .config console log report info ci-upstream-kasan-gce-root WARNING: suspicious RCU usage in unmap_page_range
2021/03/31 05:30 upstream 2bb25b3a748a 6a81331a .config console log report info ci-upstream-kasan-gce-selinux-root WARNING: suspicious RCU usage in unmap_page_range
2021/01/02 09:15 upstream f6e1ea196492 79264ae3 .config console log report info ci-qemu-upstream
2020/11/11 19:25 upstream eccc87672492 cca87986 .config console log report info ci-qemu-upstream
* Struck through repros no longer work on HEAD.