From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+3d5461510f8dc4adfe30@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kvm?] [kvm-x86?] INFO: rcu detected stall in kvm_vcpu_ioctl (4)
Date: Sat, 6 Jun 2026 14:14:59 +0800 [thread overview]
Message-ID: <20260606061501.1554-1-hdanton@sina.com> (raw)
In-Reply-To: <694f53ba.050a0220.35954c.0084.GAE@google.com>
> Date: Fri, 26 Dec 2025 19:34:18 -0800 [thread overview]
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: cc3aa43b44bd Add linux-next specific files for 20251219
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1252109a580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f7a09bf3b9133d9d
> dashboard link: https://syzkaller.appspot.com/bug?extid=3d5461510f8dc4adfe30
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14eb1022580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13cc18fc580000
#syz test
--- x/arch/x86/kvm/hyperv.c
+++ y/arch/x86/kvm/hyperv.c
@@ -657,10 +657,8 @@ static int stimer_start(struct kvm_vcpu_
stimer->index,
time_now, stimer->exp_time);
- hrtimer_start(&stimer->timer,
- ktime_add_ns(ktime_now,
- 100 * (stimer->exp_time - time_now)),
- HRTIMER_MODE_ABS);
+ hrtimer_forward_now(&stimer->timer,
+ ns_to_ktime(100 * (stimer->exp_time - time_now)));
return 0;
}
stimer->exp_time = stimer->count;
@@ -679,9 +677,7 @@ static int stimer_start(struct kvm_vcpu_
stimer->index,
time_now, stimer->count);
- hrtimer_start(&stimer->timer,
- ktime_add_ns(ktime_now, 100 * (stimer->count - time_now)),
- HRTIMER_MODE_ABS);
+ hrtimer_forward_now(&stimer->timer, ns_to_ktime(100 * (stimer->count - time_now)));
return 0;
}
--- x/drivers/nvme/host/tcp.c
+++ y/drivers/nvme/host/tcp.c
@@ -3046,6 +3046,8 @@ static int __init nvme_tcp_init_module(v
if (wq_unbound)
wq_flags |= WQ_UNBOUND;
+ else
+ wq_flags |= WQ_PERCPU;
nvme_tcp_wq = alloc_workqueue("nvme_tcp_wq", wq_flags, 0);
if (!nvme_tcp_wq)
--
next prev parent reply other threads:[~2026-06-06 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 3:34 syzbot
2026-06-05 12:14 ` Carlos López
2026-06-05 15:08 ` syzbot
2026-06-05 15:15 ` Forwarded: " syzbot
2026-06-05 21:48 ` Hillf Danton
2026-06-05 22:35 ` syzbot
2026-06-06 6:14 ` Hillf Danton [this message]
2026-06-06 6:44 ` syzbot
2026-06-06 14:11 ` Forwarded: " syzbot
[not found] <b31a5312-8b69-4d30-8d58-49f6926404da@suse.de>
2026-06-05 15:44 ` syzbot
[not found] <c7ed2214-c822-40cf-95ef-fb9ab79dedc2@suse.de>
2026-06-06 15:10 ` 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=20260606061501.1554-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3d5461510f8dc4adfe30@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
Powered by JetHome