From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Ryosuke Yasuoka <ryasuoka@redhat.com>
Cc: pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/kvm: Avoid freeing stack-allocated node in kvm_async_pf_queue_task
Date: Wed, 10 Dec 2025 15:07:34 +0100 [thread overview]
Message-ID: <875xae4ehl.fsf@redhat.com> (raw)
In-Reply-To: <20251206140939.144038-1-ryasuoka@redhat.com>
Ryosuke Yasuoka <ryasuoka@redhat.com> writes:
> kvm_async_pf_queue_task() can incorrectly try to kfree() a node
> allocated on the stack of kvm_async_pf_task_wait_schedule().
>
> This occurs when a task requests a PF while another task's PF request
> with the same token is still pending. Since the token is derived from
> the (u32)address in exc_page_fault(), two different tasks can generate
> the same token.
>
> Currently, kvm_async_pf_queue_task() assumes that any entry found in the
> list is a dummy entry and tries to kfree() it. To fix this, add a flag
> to the node structure to distinguish stack-allocated nodes, and only
> kfree() the node if it is a dummy entry.
>
> Signed-off-by: Ryosuke Yasuoka <ryasuoka@redhat.com>
> ---
>
> v2:
> Based on Vitaly's comment,
> * Update comment in kvm_async_pf_queue_task
> * Set n->dummy false in kvm_async_pf_queue_task
> * Add explanation about what token is in commit message.
>
> v1:
> https://lore.kernel.org/all/87cy4vlmv8.fsf@redhat.com/
>
>
> arch/x86/kernel/kvm.c | 19 ++++++++++++++++---
> 1 file changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
> index df78ddee0abb..37dc8465e0f5 100644
> --- a/arch/x86/kernel/kvm.c
> +++ b/arch/x86/kernel/kvm.c
> @@ -89,6 +89,7 @@ struct kvm_task_sleep_node {
> struct swait_queue_head wq;
> u32 token;
> int cpu;
> + bool dummy;
> };
>
> static struct kvm_task_sleep_head {
> @@ -120,15 +121,26 @@ static bool kvm_async_pf_queue_task(u32 token, struct kvm_task_sleep_node *n)
> raw_spin_lock(&b->lock);
> e = _find_apf_task(b, token);
> if (e) {
> - /* dummy entry exist -> wake up was delivered ahead of PF */
> - hlist_del(&e->link);
> + struct kvm_task_sleep_node *dummy = NULL;
> +
> + /*
> + * The entry can either be a 'dummy' entry (which is put on the
> + * list when wake-up happens ahead of APF handling completion)
> + * or a token from another task which should not be touched.
> + */
> + if (e->dummy) {
> + hlist_del(&e->link);
> + dummy = e;
> + }
> +
> raw_spin_unlock(&b->lock);
> - kfree(e);
> + kfree(dummy);
> return false;
> }
>
> n->token = token;
> n->cpu = smp_processor_id();
> + n->dummy = false;
> init_swait_queue_head(&n->wq);
> hlist_add_head(&n->link, &b->list);
> raw_spin_unlock(&b->lock);
> @@ -231,6 +243,7 @@ static void kvm_async_pf_task_wake(u32 token)
> }
> dummy->token = token;
> dummy->cpu = smp_processor_id();
> + dummy->dummy = true;
> init_swait_queue_head(&dummy->wq);
> hlist_add_head(&dummy->link, &b->list);
> dummy = NULL;
>
> base-commit: 416f99c3b16f582a3fc6d64a1f77f39d94b76de5
Reviewed-by: Vitaly Kuznetsov <vkuznets@redhat.com>
--
Vitaly
next prev parent reply other threads:[~2025-12-10 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 14:09 [PATCH v2] x86/kvm: Avoid freeing stack-allocated node in kvm_async_pf_queue_task Ryosuke Yasuoka
2025-12-10 14:07 ` Vitaly Kuznetsov [this message]
2025-12-23 7:38 ` Ryosuke Yasuoka
2025-12-23 8:39 ` Paolo Bonzini
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=875xae4ehl.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ryasuoka@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.