From: syzbot <syzbot+ab6273c58262b9de56d9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: [PATCH] INFO: task hung in kvm_gmem_release (2)
Date: Wed, 16 Sep 2026 18:21:35 -0700 [thread overview]
Message-ID: <6aab409f.b398a7c9.1f86be.0002.GAE@google.com> (raw)
In-Reply-To: <6aa42297.f2639fcc.29487d.002f.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] INFO: task hung in kvm_gmem_release (2)
Author: jchuang26@m.fudan.edu.cn
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 50d05c7c76c96b90462f24debacca971d2e86713
Reported-by: syzbot+ab6273c58262b9de56d9@syzkaller.appspotmail.com
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 65eb26a05..ad5852f49 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -2572,8 +2572,18 @@ static int kvm_vm_set_mem_attributes(struct kvm *kvm, gfn_t start, gfn_t end,
/*
* Reserve memory ahead of time to avoid having to deal with failures
* partway through setting the new attributes.
+ *
+ * The requested range can be arbitrarily large, so allow userspace to
+ * abort the reservation loop with a signal. Otherwise the loop can run
+ * for an extended period of time while holding slots_lock, which blocks
+ * tasks such as kvm_gmem_release() and triggers hung task warnings.
*/
for (i = start; i < end; i++) {
+ if (signal_pending(current)) {
+ r = -EINTR;
+ goto out_unlock;
+ }
+
r = xa_reserve(&kvm->mem_attr_array, i, GFP_KERNEL_ACCOUNT);
if (r)
goto out_unlock;
@@ -2612,6 +2622,14 @@ static int kvm_vm_ioctl_set_mem_attributes(struct kvm *kvm,
if (!PAGE_ALIGNED(attrs->address) || !PAGE_ALIGNED(attrs->size))
return -EINVAL;
+ /*
+ * KVM processes the range one gfn at a time while holding slots_lock.
+ * Reject absurdly large requests, using the same limit as memory
+ * regions, so that userspace can't hang tasks that need slots_lock.
+ */
+ if ((attrs->size >> PAGE_SHIFT) > KVM_MEM_MAX_NR_PAGES)
+ return -EINVAL;
+
start = attrs->address >> PAGE_SHIFT;
end = (attrs->address + attrs->size) >> PAGE_SHIFT;
prev parent reply other threads:[~2026-09-17 1:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 15:47 [syzbot] [kvm?] " syzbot
2026-09-11 23:02 ` Sean Christopherson
2026-09-14 11:00 ` Forwarded: [PATCH] " syzbot
2026-09-15 1:38 ` syzbot
2026-09-17 1:15 ` syzbot
2026-09-17 1:21 ` syzbot [this message]
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=6aab409f.b398a7c9.1f86be.0002.GAE@google.com \
--to=syzbot+ab6273c58262b9de56d9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®