From: syzbot <syzbot+12b178b7c756664d2518@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tbsthitw@gmail.com
Subject: Re: [syzbot] [kvmarm] BUG: scheduling while atomic in __synchronize_srcu
Date: Thu, 30 Apr 2026 11:49:02 -0700 [thread overview]
Message-ID: <69f3a41e.050a0220.22f9df.001b.GAE@google.com> (raw)
In-Reply-To: <20260501022749.010441@splitlinedeMacBook-Pro.local>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: scheduling while atomic in __synchronize_srcu
BUG: scheduling while atomic: syz.2.18/4067/0x00000002
Modules linked in:
CPU: 1 UID: 0 PID: 4067 Comm: syz.2.18 Not tainted syzkaller #0 PREEMPT
Hardware name: linux,dummy-virt (DT)
Call trace:
dump_backtrace arch/arm64/kernel/stacktrace.c:498 [inline] (C)
show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x60/0x80 lib/dump_stack.c:120
dump_stack+0x18/0x24 lib/dump_stack.c:129
__schedule_bug+0x54/0x78 kernel/sched/core.c:5936
schedule_debug kernel/sched/core.c:5963 [inline]
__schedule+0x89c/0xddc kernel/sched/core.c:7038
__schedule_loop kernel/sched/core.c:7267 [inline]
schedule+0x34/0x11c kernel/sched/core.c:7282
schedule_timeout+0xd4/0x110 kernel/time/sleep_timeout.c:75
do_wait_for_common kernel/sched/completion.c:100 [inline]
__wait_for_common kernel/sched/completion.c:121 [inline]
wait_for_common kernel/sched/completion.c:132 [inline]
wait_for_completion+0x78/0x160 kernel/sched/completion.c:153
__synchronize_srcu+0x90/0xd0 kernel/rcu/srcutree.c:1496
synchronize_srcu_expedited+0x24/0x40 kernel/rcu/srcutree.c:1521
kvm_set_irq_routing+0x204/0x294 virt/kvm/irqchip.c:225
kvm_vgic_setup_default_irq_routing+0x84/0xb0 arch/arm64/kvm/vgic/vgic-irqfd.c:153
vgic_init+0x1cc/0x2d8 arch/arm64/kvm/vgic/vgic-init.c:481
vgic_lazy_init+0x54/0x70 arch/arm64/kvm/vgic/vgic-init.c:610
kvm_vgic_inject_irq+0x30/0x188 arch/arm64/kvm/vgic/vgic.c:539
kvm_timer_update_irq+0x88/0xf8 arch/arm64/kvm/arch_timer.c:467
kvm_timer_vcpu_reset+0xd8/0x1e0 arch/arm64/kvm/arch_timer.c:1059
kvm_reset_vcpu+0x194/0x360 arch/arm64/kvm/reset.c:268
kvm_vcpu_set_target arch/arm64/kvm/arm.c:1681 [inline]
kvm_arch_vcpu_ioctl_vcpu_init arch/arm64/kvm/arm.c:1701 [inline]
kvm_arch_vcpu_ioctl+0x2f0/0x8d8 arch/arm64/kvm/arm.c:1822
kvm_vcpu_ioctl+0x4a0/0x8e4 virt/kvm/kvm_main.c:4646
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__arm64_sys_ioctl+0xac/0x104 fs/ioctl.c:583
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x54/0x10c arch/arm64/kernel/syscall.c:49
el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:121
do_el0_svc+0x1c/0x34 arch/arm64/kernel/syscall.c:140
el0_svc+0x38/0x15c arch/arm64/kernel/entry-common.c:723
el0t_64_sync_handler+0xa0/0xf0 arch/arm64/kernel/entry-common.c:742
el0t_64_sync+0x1a4/0x1a8 arch/arm64/kernel/entry.S:594
BUG: scheduling while atomic: syz.2.18/4067/0x00000000
Modules linked in:
CPU: 1 UID: 0 PID: 4067 Comm: syz.2.18 Tainted: G W syzkaller #0 PREEMPT
Tainted: [W]=WARN
Hardware name: linux,dummy-virt (DT)
Call trace:
dump_backtrace arch/arm64/kernel/stacktrace.c:498 [inline] (C)
show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x60/0x80 lib/dump_stack.c:120
dump_stack+0x18/0x24 lib/dump_stack.c:129
__schedule_bug+0x54/0x78 kernel/sched/core.c:5936
schedule_debug kernel/sched/core.c:5963 [inline]
__schedule+0x89c/0xddc kernel/sched/core.c:7038
__schedule_loop kernel/sched/core.c:7267 [inline]
schedule+0x34/0x11c kernel/sched/core.c:7282
futex_do_wait kernel/futex/waitwake.c:358 [inline]
__futex_wait+0xf0/0x178 kernel/futex/waitwake.c:691
futex_wait+0x88/0x118 kernel/futex/waitwake.c:719
do_futex+0xf8/0x1a0 kernel/futex/syscalls.c:130
__do_sys_futex kernel/futex/syscalls.c:207 [inline]
__se_sys_futex kernel/futex/syscalls.c:188 [inline]
__arm64_sys_futex+0xfc/0x1a0 kernel/futex/syscalls.c:188
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x54/0x10c arch/arm64/kernel/syscall.c:49
el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:121
do_el0_svc+0x1c/0x34 arch/arm64/kernel/syscall.c:140
el0_svc+0x38/0x15c arch/arm64/kernel/entry-common.c:723
el0t_64_sync_handler+0xa0/0xf0 arch/arm64/kernel/entry-common.c:742
el0t_64_sync+0x1a4/0x1a8 arch/arm64/kernel/entry.S:594
Tested on:
commit: 08d0d346 Merge tag 'net-7.1-rc2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15a2f2d2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9475bd041c93289
dashboard link: https://syzkaller.appspot.com/bug?extid=12b178b7c756664d2518
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1142f2d2580000
next parent reply other threads:[~2026-04-30 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260501022749.010441@splitlinedeMacBook-Pro.local>
2026-04-30 18:49 ` syzbot [this message]
[not found] <20260501025346.021842@splitlinedeMacBook-Pro.local>
2026-04-30 19:51 ` [syzbot] [kvmarm] BUG: scheduling while atomic in __synchronize_srcu syzbot
[not found] <20260501014126.083462@splitlinedeMacBook-Pro.local>
2026-04-30 17:51 ` syzbot
[not found] <20260501012551.074994@splitlinedeMacBook-Pro.local>
2026-04-30 17:36 ` syzbot
[not found] <20260501000552.017783@splitlinedeMacBook-Pro.local>
2026-04-30 16:15 ` syzbot
[not found] <86wly527p7.wl-maz@kernel.org>
2026-04-17 10:39 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69f3a41e.050a0220.22f9df.001b.GAE@google.com \
--to=syzbot+12b178b7c756664d2518@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tbsthitw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox