From: Liu Yuan <namei.unix@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: mitake.hitoshi@lab.ntt.co.jp, kwolf@redhat.com,
sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] sheepdog: Fix misleading error messages in sd_snapshot_create()
Date: Fri, 13 Feb 2015 11:57:16 +0800 [thread overview]
Message-ID: <20150213035716.GB21936@ubuntu-trusty> (raw)
In-Reply-To: <1423748990-9709-1-git-send-email-armbru@redhat.com>
On Thu, Feb 12, 2015 at 02:49:50PM +0100, Markus Armbruster wrote:
> If do_sd_create() fails, it first reports the error returned, then
> reports a another one with strerror(errno). errno is meaningless at
> that point.
>
> Report just one error combining the valid information from both
> messages.
>
> Reported-by: Eric Blake <eblake@redhat.com>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> Applies on top of my "[PATCH v2 00/10] Clean up around
> error_get_pretty(), qerror_report_err()", but rebasing to master would
> be trivial.
>
> block/sheepdog.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index 6a4a3bd..0e8c712 100644
> --- a/block/sheepdog.c
> +++ b/block/sheepdog.c
> @@ -2225,9 +2225,8 @@ static int sd_snapshot_create(BlockDriverState *bs, QEMUSnapshotInfo *sn_info)
>
> ret = do_sd_create(s, &new_vid, 1, &local_err);
> if (ret < 0) {
> - error_report_err(local_err);
> - error_report("failed to create inode for snapshot. %s",
> - strerror(errno));
> + error_report("failed to create inode for snapshot: %s",
> + error_get_pretty(local_err));
> goto cleanup;
> }
Reviewed-by: Liu Yuan <namei.unix@gmail.com>
next prev parent reply other threads:[~2015-02-13 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 13:49 [Qemu-devel] [PATCH] sheepdog: Fix misleading error messages in sd_snapshot_create() Markus Armbruster
2015-02-12 15:15 ` Eric Blake
2015-02-13 3:57 ` Liu Yuan [this message]
2015-02-27 12:56 ` Markus Armbruster
2015-03-04 13:03 ` Kevin Wolf
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=20150213035716.GB21936@ubuntu-trusty \
--to=namei.unix@gmail.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@redhat.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).