From: Paolo Bonzini <pbonzini@redhat.com>
To: riegamaths@gmail.com
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] block: output more error messages if failed to create temporary snapshot
Date: Wed, 05 Sep 2012 17:40:57 +0200 [thread overview]
Message-ID: <50477289.5070703@redhat.com> (raw)
In-Reply-To: <1346851493-9149-1-git-send-email-riegamaths@gmail.com>
Il 05/09/2012 15:24, riegamaths@gmail.com ha scritto:
> From: Dunrong Huang <riegamaths@gmail.com>
>
> If we failed to create temporary snapshot, the error message did not match
> with the error, for example:
>
> $ TMPDIR=/tmp/bad_path qemu-system-x86_64 -enable-kvm debian.qcow2 -snapshot
> qemu-system-x86_64: -enable-kvm: could not open disk image /home/mathslinux/Images/debian.qcow2: No such file or directory
>
> Indeed, the file which cant be created is /tmp/bad_path/vl.xxxxxx, not
> debian.qcow2. so the error message makes users feel confused.
>
> Signed-off-by: Dunrong Huang <riegamaths@gmail.com>
> ---
> v1 -> v2:
> Output error message only if fd < 0
> v2 -> v3:
> Output error message in the caller of get_tmp_filename()
> block.c | 2 ++
> 1 个文件被修改,插入 2 行(+)
>
> diff --git a/block.c b/block.c
> index 470bdcc..074987e 100644
> --- a/block.c
> +++ b/block.c
> @@ -764,6 +764,8 @@ int bdrv_open(BlockDriverState *bs, const char *filename, int flags,
>
> ret = get_tmp_filename(tmp_filename, sizeof(tmp_filename));
> if (ret < 0) {
> + fprintf(stderr, "Could not create temporary snapshot %s: %s\n",
> + tmp_filename, strerror(errno));
> return ret;
> }
>
>
Looks good.
Paolo
next prev parent reply other threads:[~2012-09-05 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 13:24 [Qemu-devel] [PATCH v3] block: output more error messages if failed to create temporary snapshot riegamaths
2012-09-05 15:40 ` Paolo Bonzini [this message]
2012-09-07 13:12 ` 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=50477289.5070703@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riegamaths@gmail.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).