From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 4/8] block: bdrv_img_create(): add Error ** argument
Date: Thu, 18 Oct 2012 14:08:05 +0200 [thread overview]
Message-ID: <507FF125.2040201@redhat.com> (raw)
In-Reply-To: <1350502556-4885-5-git-send-email-lcapitulino@redhat.com>
Am 17.10.2012 21:35, schrieb Luiz Capitulino:
> This commit adds an Error ** argument to bdrv_img_create() and set it
> appropriately on error.
>
> Callers of bdrv_img_create() pass NULL for the new argument and still
> rely on bdrv_img_create()'s return value. Next commits will change
> callers to use the Error object instead.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> block.c | 23 +++++++++++++++++++++--
> block.h | 2 +-
> blockdev.c | 2 +-
> qemu-img.c | 2 +-
> 4 files changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/block.c b/block.c
> index bdb53af..83bcab5 100644
> --- a/block.c
> +++ b/block.c
> @@ -4295,7 +4295,7 @@ bdrv_acct_done(BlockDriverState *bs, BlockAcctCookie *cookie)
> int bdrv_img_create(const char *filename, const char *fmt,
> const char *base_filename, const char *base_fmt,
> char *options, uint64_t img_size, int flags,
> - QEMUOptionParameter **param_list)
> + QEMUOptionParameter **param_list, Error **errp)
> {
> QEMUOptionParameter *param = NULL, *create_options = NULL;
> QEMUOptionParameter *backing_fmt, *backing_file, *size;
> @@ -4308,6 +4308,7 @@ int bdrv_img_create(const char *filename, const char *fmt,
> drv = bdrv_find_format(fmt);
> if (!drv) {
> error_report("Unknown file format '%s'", fmt);
> + error_setg(errp, "Unknown file format '%s'", fmt);
> ret = -EINVAL;
> goto out;
> }
> @@ -4315,6 +4316,7 @@ int bdrv_img_create(const char *filename, const char *fmt,
> proto_drv = bdrv_find_protocol(filename);
> if (!proto_drv) {
> error_report("Unknown protocol '%s'", filename);
> + error_setg(errp, "Unknown protocol '%s'", filename);
> ret = -EINVAL;
> goto out;
> }
> @@ -4334,6 +4336,7 @@ int bdrv_img_create(const char *filename, const char *fmt,
> param = parse_option_parameters(options, create_options, param);
> if (param == NULL) {
> error_report("Invalid options for file format '%s'.", fmt);
> + error_setg(errp, "Invalid options for file format '%s'.", fmt);
> ret = -EINVAL;
> goto out;
> }
> @@ -4344,6 +4347,8 @@ int bdrv_img_create(const char *filename, const char *fmt,
> base_filename)) {
> error_report("Backing file not supported for file format '%s'",
> fmt);
> + error_setg(errp, "Backing file not supported for file format '%s'",
> + fmt);
> ret = -EINVAL;
> goto out;
> }
> @@ -4353,6 +4358,8 @@ int bdrv_img_create(const char *filename, const char *fmt,
> if (set_option_parameter(param, BLOCK_OPT_BACKING_FMT, base_fmt)) {
> error_report("Backing file format not supported for file "
> "format '%s'", fmt);
> + error_setg(errp, "Backing file format not supported for file "
> + "format '%s'", fmt);
> ret = -EINVAL;
> goto out;
> }
> @@ -4363,6 +4370,8 @@ int bdrv_img_create(const char *filename, const char *fmt,
> if (!strcmp(filename, backing_file->value.s)) {
> error_report("Error: Trying to create an image with the "
> "same filename as the backing file");
> + error_setg(errp, "Error: Trying to create an image with the "
> + "same filename as the backing file");
> ret = -EINVAL;
> goto out;
> }
> @@ -4374,6 +4383,8 @@ int bdrv_img_create(const char *filename, const char *fmt,
> if (!backing_drv) {
> error_report("Unknown backing file format '%s'",
> backing_fmt->value.s);
> + error_setg(errp, "Unknown backing file format '%s'",
> + backing_fmt->value.s);
> ret = -EINVAL;
> goto out;
> }
> @@ -4396,7 +4407,8 @@ int bdrv_img_create(const char *filename, const char *fmt,
>
> ret = bdrv_open(bs, backing_file->value.s, back_flags, backing_drv);
> if (ret < 0) {
> - error_report("Could not open '%s'", backing_file->value.s);
This is the only error_report() that is dropped in this patch. Not sure
what is the best patch to drop them, but consistency wouldn't hurt.
If we want to keep the series bisectable, i.e. qemu-img output stays the
same for each patch, you'd have to drop them in 5/8, I think.
Kevin
next prev parent reply other threads:[~2012-10-18 12:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 19:35 [Qemu-devel] [PATCH 0/8] block: bdrv_img_create(): propagate errors Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 1/8] error: add error_set_errno and error_setg_errno Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 2/8] block: bdrv_img_create(): add param_list argument Luiz Capitulino
2012-10-18 11:57 ` Kevin Wolf
2012-10-18 13:33 ` Luiz Capitulino
2012-10-18 17:18 ` Luiz Capitulino
2012-10-19 9:13 ` Kevin Wolf
2012-10-19 12:49 ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 3/8] block: bdrv_img_create(): move parameter list printing to qemu-img Luiz Capitulino
2012-10-18 12:01 ` Kevin Wolf
2012-10-18 12:16 ` Kevin Wolf
2012-10-18 13:34 ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 4/8] block: bdrv_img_create(): add Error ** argument Luiz Capitulino
2012-10-18 12:08 ` Kevin Wolf [this message]
2012-10-18 13:41 ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 5/8] qemu-img: img_create(): use Error object Luiz Capitulino
2012-10-18 12:11 ` Kevin Wolf
2012-10-18 13:49 ` Luiz Capitulino
2012-10-18 14:02 ` Kevin Wolf
2012-10-23 9:58 ` Markus Armbruster
2012-10-23 10:08 ` Kevin Wolf
2012-10-23 13:07 ` Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 6/8] qemu-img: img_create(): simplify Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 7/8] qmp: qmp_transaction(): pass Error object to bdrv_img_create() Luiz Capitulino
2012-10-17 19:35 ` [Qemu-devel] [PATCH 8/8] block: bdrv_img_create(): drop unused error handling code Luiz Capitulino
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=507FF125.2040201@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).