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>,
qemu-block@nongnu.org, Eric Blake <eblake@redhat.com>
Subject: [PATCH v2 03/29] block: Fix missing ERRP_GUARD() for error_prepend()
Date: Mon, 11 Mar 2024 11:37:56 +0800 [thread overview]
Message-ID: <20240311033822.3142585-4-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].
In block.c, there are 4 functions passing @errp to error_prepend()
without ERRP_GUARD():
- bdrv_co_create_opts_simple()
- parse_json_filename()
- bdrv_open_backing_file()
- bdrv_append_temp_snapshot()
bdrv_co_create_opts_simple(), is an implementation of
BlockDriver.bdrv_co_create_opts(). There are too many possible callers
to check the impact of this defect; it may or may not be harmless. Thus
it is necessary to protect @errp with ERRP_GUARD().
Though the @errp parameters passed to parse_json_filename(),
bdrv_open_backing_file() and bdrv_append_temp_snapshot() points to their
callers' local_err, to follow the requirement of @errp, also add missing
ERRP_GUARD() at their beginning.
[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: qemu-block@nongnu.org
Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
v2:
* Use Markus' sentence to polish commit message. (Markus)
* Fix typo. (Eric)
---
block.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/block.c b/block.c
index 1ed9214f66ed..cf66c767a011 100644
--- a/block.c
+++ b/block.c
@@ -633,6 +633,7 @@ int coroutine_fn bdrv_co_create_opts_simple(BlockDriver *drv,
QemuOpts *opts,
Error **errp)
{
+ ERRP_GUARD();
BlockBackend *blk;
QDict *options;
int64_t size = 0;
@@ -1998,6 +1999,7 @@ fail_opts:
static QDict *parse_json_filename(const char *filename, Error **errp)
{
+ ERRP_GUARD();
QObject *options_obj;
QDict *options;
int ret;
@@ -3585,6 +3587,7 @@ int bdrv_set_backing_hd(BlockDriverState *bs, BlockDriverState *backing_hd,
int bdrv_open_backing_file(BlockDriverState *bs, QDict *parent_options,
const char *bdref_key, Error **errp)
{
+ ERRP_GUARD();
char *backing_filename = NULL;
char *bdref_key_dot;
const char *reference = NULL;
@@ -3851,6 +3854,7 @@ static BlockDriverState *bdrv_append_temp_snapshot(BlockDriverState *bs,
QDict *snapshot_options,
Error **errp)
{
+ ERRP_GUARD();
g_autofree char *tmp_filename = NULL;
int64_t total_size;
QemuOpts *opts = NULL;
--
2.34.1
next prev parent reply other threads:[~2024-03-11 3:28 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 ` Zhao Liu [this message]
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 ` [PATCH v2 07/29] block/qcow2-bitmap: " Zhao Liu
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-4-zhao1.liu@linux.intel.com \
--to=zhao1.liu@linux.intel.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@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=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).