qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Zhao Liu" <zhao1.liu@linux.intel.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Zhao Liu <zhao1.liu@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 16/17] target/i386/sev: Fix missing ERRP_GUARD() for error_prepend()
Date: Thu, 29 Feb 2024 18:36:12 +0100	[thread overview]
Message-ID: <f3d3a29d-a78d-4f39-b5a2-9c64ba9718a2@redhat.com> (raw)
In-Reply-To: <20240229143914.1977550-17-zhao1.liu@linux.intel.com>

On 29/02/2024 15.39, Zhao Liu wrote:
> From: Zhao Liu <zhao1.liu@intel.com>
> 
> As the comment in qapi/error, passing @errp to error_prepend() requires
> ERRP_GUARD():
> 
> * = Why, when and how to use ERRP_GUARD() =
> *
> * Without ERRP_GUARD(), use of the @errp parameter is restricted:
> ...
> * - It should not be passed to error_prepend(), error_vprepend() or
> *   error_append_hint(), because that doesn't work with &error_fatal.
> * ERRP_GUARD() lifts these restrictions.
> *
> * To use ERRP_GUARD(), add it right at the beginning of the function.
> * @errp can then be used without worrying about the argument being
> * NULL or &error_fatal.
> 
> ERRP_GUARD() could avoid the case when @errp is the pointer of
> error_fatal, the user can't see this additional information, because
> exit() happens in error_setg earlier than information is added [1].
> 
> The sev_inject_launch_secret() passes @errp to error_prepend(), and as
> an APIs defined in target/i386/sev.h, it is necessary to protect its
> @errp with ERRP_GUARD().
> 
> To avoid the issue like [1] said, add missing ERRP_GUARD() at the
> beginning of this function.
> 
> [1]: Issue description in the commit message of commit ae7c80a7bd73
>       ("error: New macro ERRP_GUARD()").
> 
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> ---
>   target/i386/sev.c | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/target/i386/sev.c b/target/i386/sev.c
> index 173de91afe7d..72930ff0dcc5 100644
> --- a/target/i386/sev.c
> +++ b/target/i386/sev.c
> @@ -1044,6 +1044,7 @@ sev_encrypt_flash(uint8_t *ptr, uint64_t len, Error **errp)
>   int sev_inject_launch_secret(const char *packet_hdr, const char *secret,
>                                uint64_t gpa, Error **errp)
>   {
> +    ERRP_GUARD();
>       struct kvm_sev_launch_secret input;
>       g_autofree guchar *data = NULL, *hdr = NULL;
>       int error, ret = 1;

Reviewed-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2024-02-29 17:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 14:38 [PATCH 00/17 Part 2] Cleanup up to fix missing ERRP_GUARD() for error_prepend() Zhao Liu
2024-02-29 14:38 ` [PATCH 01/17] hw/misc/ivshmem: Fix " Zhao Liu
2024-02-29 17:23   ` Thomas Huth
2024-03-01  6:41     ` Zhao Liu
2024-02-29 14:38 ` [PATCH 02/17] hw/net/xen_nic: " Zhao Liu
2024-02-29 17:25   ` Thomas Huth
2024-03-08 15:26     ` Anthony PERARD
2024-02-29 14:39 ` [PATCH 03/17] hw/remote/remote-obj: hw/misc/ivshmem: " Zhao Liu
2024-02-29 17:26   ` Thomas Huth
2024-02-29 14:39 ` [PATCH 04/17] hw/scsi/vhost-scsi: " Zhao Liu
2024-02-29 17:22   ` Thomas Huth
2024-03-01  6:42     ` Zhao Liu
2024-02-29 14:39 ` [PATCH 05/17] hw/vfio/ap: " Zhao Liu
2024-02-29 17:30   ` Thomas Huth
2024-03-04 15:12     ` Anthony Krowiak
2024-03-07 19:25       ` Thomas Huth
2024-03-08 11:39         ` Zhao Liu
2024-02-29 14:39 ` [PATCH 06/17] hw/vfio/container: " Zhao Liu
2024-02-29 17:28   ` Thomas Huth
2024-02-29 18:21   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 07/17] hw/vfio/helpers: " Zhao Liu
2024-02-29 18:22   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 08/17] hw/vfio/iommufd: " Zhao Liu
2024-02-29 18:23   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 09/17] hw/vfio/pci-quirks: " Zhao Liu
2024-02-29 18:23   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 10/17] hw/vfio/pci: " Zhao Liu
2024-02-29 18:25   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 11/17] hw/vfio/platform: " Zhao Liu
2024-02-29 18:25   ` Cédric Le Goater
2024-02-29 14:39 ` [PATCH 12/17] hw/virtio/vhost-vsock: " Zhao Liu
2024-02-29 14:39 ` [PATCH 13/17] hw/virtio/vhost: " Zhao Liu
2024-02-29 14:39 ` [PATCH 14/17] migration/option: " Zhao Liu
2024-02-29 14:39   ` Fabiano Rosas
2024-03-01  1:37   ` Peter Xu
2024-02-29 14:39 ` [PATCH 15/17] net/vhost-vdpa: " Zhao Liu
2024-02-29 17:33   ` Thomas Huth
2024-02-29 14:39 ` [PATCH 16/17] target/i386/sev: " Zhao Liu
2024-02-29 17:36   ` Thomas Huth [this message]
2024-02-29 14:39 ` [PATCH 17/17] target/s390x/cpu_models: " Zhao Liu
2024-02-29 17:17   ` Thomas Huth
2024-03-01  6:46     ` Zhao Liu
2024-03-08 10:12     ` Zhao Liu
2024-03-08 10:08       ` Thomas Huth

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=f3d3a29d-a78d-4f39-b5a2-9c64ba9718a2@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhao1.liu@intel.com \
    --cc=zhao1.liu@linux.intel.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;
as well as URLs for NNTP newsgroup(s).