qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@linux.intel.com>
To: "Thomas Huth" <thuth@redhat.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>,
	Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
	Eric Blake <eblake@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	John Snow <jsnow@redhat.com>,
	qemu-block@nongnu.org
Subject: [PATCH v2 07/29] block/qcow2-bitmap: Fix missing ERRP_GUARD() for error_prepend()
Date: Mon, 11 Mar 2024 11:38:00 +0800	[thread overview]
Message-ID: <20240311033822.3142585-8-zhao1.liu@linux.intel.com> (raw)
In-Reply-To: <20240311033822.3142585-1-zhao1.liu@linux.intel.com>

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 &error_fatal, the user
can't see this additional information, because exit() happens in
error_setg earlier than information is added [1].

The qcow2_co_can_store_new_dirty_bitmap() passes @errp to
error_prepend(). As a BlockDriver.bdrv_co_can_store_new_dirty_bitmap
method, it's called by bdrv_co_can_store_new_dirty_bitmap().

Its caller is not being called anywhere, but as the API in
include/block/block-io.h, we can't ensure what kind of @errp future
users will pass in.

To avoid potential issues as [1] said, add missing ERRP_GUARD() at the
beginning of qcow2_co_can_store_new_dirty_bitmap().

[1]: Issue description in the commit message of commit ae7c80a7bd73
     ("error: New macro ERRP_GUARD()").

Cc: Kevin Wolf <kwolf@redhat.com>
Cc: Hanna Reitz <hreitz@redhat.com>
Cc: Eric Blake <eblake@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
---
 block/qcow2-bitmap.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/block/qcow2-bitmap.c b/block/qcow2-bitmap.c
index 0e567ed588d7..874ea5694851 100644
--- a/block/qcow2-bitmap.c
+++ b/block/qcow2-bitmap.c
@@ -1710,6 +1710,7 @@ bool coroutine_fn qcow2_co_can_store_new_dirty_bitmap(BlockDriverState *bs,
                                                       uint32_t granularity,
                                                       Error **errp)
 {
+    ERRP_GUARD();
     BDRVQcow2State *s = bs->opaque;
     BdrvDirtyBitmap *bitmap;
     uint64_t bitmap_directory_size = 0;
-- 
2.34.1



  parent reply	other threads:[~2024-03-11  3:26 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  3:37 [PATCH v2 00/29] Cleanup up to fix missing ERRP_GUARD() for error_prepend() Zhao Liu
2024-03-11  3:37 ` [PATCH v2 01/29] error: Add error_vprepend() in comment of ERRP_GUARD() rules Zhao Liu
2024-03-11  3:37 ` [PATCH v2 02/29] backends/iommufd: Fix missing ERRP_GUARD() for error_prepend() Zhao Liu
2024-03-11  9:32   ` Eric Auger
2024-03-11  3:37 ` [PATCH v2 03/29] block: " Zhao Liu
2024-03-11  3:37 ` [PATCH v2 04/29] block/copy-before-write: " Zhao Liu
2024-03-11  3:37 ` [PATCH v2 05/29] block/nbd: " Zhao Liu
2024-03-11  3:37 ` [PATCH v2 06/29] block/nvme: " Zhao Liu
2024-03-11  3:38 ` Zhao Liu [this message]
2024-03-11  3:38 ` [PATCH v2 08/29] block/qcow2: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 09/29] block/qed: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 10/29] block/snapshot: " Zhao Liu
2024-03-12  8:11   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 11/29] block/vdi: " Zhao Liu
2024-03-12  8:14   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 12/29] block/vmdk: " Zhao Liu
2024-03-12  8:23   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 13/29] block/virtio-blk: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 14/29] hw/core/loader-fit: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 15/29] hw/core/qdev-properties-system: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 16/29] hw/misc/ivshmem: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 17/29] hw/scsi/vhost-scsi: " Zhao Liu
2024-03-12  8:48   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 18/29] hw/vfio/ap: " Zhao Liu
2024-03-11  7:42   ` Cédric Le Goater
2024-03-11  3:38 ` [PATCH v2 19/29] hw/vfio/container: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 20/29] hw/vfio/helpers: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 21/29] hw/vfio/iommufd: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 22/29] hw/vfio/pci-quirks: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 23/29] hw/vfio/pci: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 24/29] hw/vfio/platform: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 25/29] hw/virtio/vhost-vsock: " Zhao Liu
2024-03-12  8:53   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 26/29] hw/virtio/vhost: " Zhao Liu
2024-03-12  9:09   ` Thomas Huth
2024-03-11  3:38 ` [PATCH v2 27/29] migration/option: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 28/29] net/vhost-vdpa: " Zhao Liu
2024-03-11  3:38 ` [PATCH v2 29/29] target/s390x/cpu_models: " Zhao Liu
2024-03-11  7:41   ` Cédric Le Goater
2024-03-11  7:42   ` Cédric Le Goater
2024-03-12  8:17 ` [PATCH v2 00/29] Cleanup up to fix " Philippe Mathieu-Daudé
2024-03-12  8:43   ` Zhao Liu
2024-03-12  8:50     ` Thomas Huth
2024-03-12 10:26       ` Zhao Liu
2024-03-12 10:42         ` 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=20240311033822.3142585-8-zhao1.liu@linux.intel.com \
    --to=zhao1.liu@linux.intel.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=philmd@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    --cc=zhao1.liu@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).