From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: "Carlos López" <clopez@suse.de>,
kvm@vger.kernel.org, seanjc@google.com, pbonzini@redhat.com
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] KVM: SEV: use mutex guard in snp_launch_update()
Date: Tue, 30 Dec 2025 15:10:43 +0100 [thread overview]
Message-ID: <c589418d-dc2e-4229-8f3c-fb49d8f9c45a@amd.com> (raw)
In-Reply-To: <20251219114238.3797364-2-clopez@suse.de>
> Simplify the error paths in snp_launch_update() by using a mutex guard,
> allowing early return instead of using gotos.
>
> Signed-off-by: Carlos López <clopez@suse.de>
> ---
> arch/x86/kvm/svm/sev.c | 32 +++++++++++++-------------------
> 1 file changed, 13 insertions(+), 19 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
> index f59c65abe3cf..1b325ae61d15 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -8,6 +8,7 @@
> */
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>
> +#include <linux/cleanup.h>
This does not seem to be required, as compiling without this as well.
Otherwise looks fine:
Reviewed-by: Pankaj Gupta <pankaj.gupta@amd.com>
> #include <linux/kvm_types.h>
> #include <linux/kvm_host.h>
> #include <linux/kernel.h>
> @@ -2367,7 +2368,6 @@ static int snp_launch_update(struct kvm *kvm, struct kvm_sev_cmd *argp)
> struct kvm_memory_slot *memslot;
> long npages, count;
> void __user *src;
> - int ret = 0;
>
> if (!sev_snp_guest(kvm) || !sev->snp_context)
> return -EINVAL;
> @@ -2407,13 +2407,11 @@ static int snp_launch_update(struct kvm *kvm, struct kvm_sev_cmd *argp)
> * initial expected state and better guard against unexpected
> * situations.
> */
> - mutex_lock(&kvm->slots_lock);
> + guard(mutex)(&kvm->slots_lock);
>
> memslot = gfn_to_memslot(kvm, params.gfn_start);
> - if (!kvm_slot_has_gmem(memslot)) {
> - ret = -EINVAL;
> - goto out;
> - }
> + if (!kvm_slot_has_gmem(memslot))
> + return -EINVAL;
>
> sev_populate_args.sev_fd = argp->sev_fd;
> sev_populate_args.type = params.type;
> @@ -2425,22 +2423,18 @@ static int snp_launch_update(struct kvm *kvm, struct kvm_sev_cmd *argp)
> argp->error = sev_populate_args.fw_error;
> pr_debug("%s: kvm_gmem_populate failed, ret %ld (fw_error %d)\n",
> __func__, count, argp->error);
> - ret = -EIO;
> - } else {
> - params.gfn_start += count;
> - params.len -= count * PAGE_SIZE;
> - if (params.type != KVM_SEV_SNP_PAGE_TYPE_ZERO)
> - params.uaddr += count * PAGE_SIZE;
> -
> - ret = 0;
> - if (copy_to_user(u64_to_user_ptr(argp->data), ¶ms, sizeof(params)))
> - ret = -EFAULT;
> + return -EIO;
> }
>
> -out:
> - mutex_unlock(&kvm->slots_lock);
> + params.gfn_start += count;
> + params.len -= count * PAGE_SIZE;
> + if (params.type != KVM_SEV_SNP_PAGE_TYPE_ZERO)
> + params.uaddr += count * PAGE_SIZE;
>
> - return ret;
> + if (copy_to_user(u64_to_user_ptr(argp->data), ¶ms, sizeof(params)))
> + return -EFAULT;
> +
> + return 0;
> }
>
> static int snp_launch_update_vmsa(struct kvm *kvm, struct kvm_sev_cmd *argp)
next prev parent reply other threads:[~2025-12-30 14:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 11:41 [PATCH 0/6] KVM: SEV: use mutex guards for simpler error handling Carlos López
2025-12-19 11:41 ` [PATCH 1/6] KVM: SEV: use mutex guard in snp_launch_update() Carlos López
2025-12-30 14:10 ` Gupta, Pankaj [this message]
2025-12-19 11:41 ` [PATCH 2/6] KVM: SEV: use mutex guard in sev_mem_enc_ioctl() Carlos López
2025-12-30 14:16 ` Gupta, Pankaj
2025-12-19 11:41 ` [PATCH 3/6] KVM: SEV: use mutex guard in sev_mem_enc_register_region() Carlos López
2025-12-19 11:41 ` [PATCH 4/6] KVM: SEV: use mutex guard in sev_mem_enc_unregister_region() Carlos López
2025-12-30 14:18 ` Gupta, Pankaj
2025-12-19 11:42 ` [PATCH 5/6] KVM: SEV: use mutex guard in snp_handle_guest_req() Carlos López
2025-12-30 14:20 ` Gupta, Pankaj
2025-12-19 11:42 ` [PATCH 6/6] KVM: SEV: use scoped mutex guard in sev_asid_new() Carlos López
2025-12-30 14:30 ` [PATCH 0/6] KVM: SEV: use mutex guards for simpler error handling Gupta, Pankaj
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=c589418d-dc2e-4229-8f3c-fb49d8f9c45a@amd.com \
--to=pankaj.gupta@amd.com \
--cc=bp@alien8.de \
--cc=clopez@suse.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=seanjc@google.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 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®