From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3] Improve error handling in do_snapshot_blkdev()
Date: Mon, 07 Mar 2011 17:39:39 +0100 [thread overview]
Message-ID: <4D750A4B.1070304@redhat.com> (raw)
In-Reply-To: <4D75092F.1020107@codemonkey.ws>
On 03/07/11 17:34, Anthony Liguori wrote:
> On 03/07/2011 09:27 AM, Jes.Sorensen@redhat.com wrote:
>> if (ret != 0) {
>> - abort();
>> + qerror_report(QERR_OPEN_FILE_FAILED, filename);
>> + error_printf("do_snapshot_blkdev(): Unable to open newly
>> created "
>> + "snapshot file: \n");
>> + error_printf("%s. Attempting to revert to original image: %s\n",
>> + filename, old_filename);
>
> You can't combine qerror_report with continued action. qerror_report()
> should be a terminal action. You also shouldn't combine error_printf()
> with qerror_report().
>
> You should restore the original image file before doing qerror_report()
> and just drop the error_printf()s as it's all redundant information.
I would hardly consider it redundant information that it failed and we
try to go back to the original image. That is an error in itself, even
though rolling back is better than abort()ing.
If qerror_report() is a fatal situation, that is problematic. Then we
need qerror_warn() or something as well, which can return non fatal
information.
The printfs are very valuable for the human monitor, but it isn't really
clear to me what is the ideal return value.
Cheers,
Jes
next prev parent reply other threads:[~2011-03-07 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 15:27 [Qemu-devel] [PATCH v3] Improve error handling in do_snapshot_blkdev() Jes.Sorensen
2011-03-07 15:44 ` [Qemu-devel] " Kevin Wolf
2011-03-07 16:34 ` [Qemu-devel] " Anthony Liguori
2011-03-07 16:39 ` Jes Sorensen [this message]
2011-03-07 17:47 ` Anthony Liguori
2011-03-08 8:24 ` Jes Sorensen
2011-03-08 13:42 ` Anthony Liguori
2011-03-08 16:44 ` Jes Sorensen
2011-03-08 17:46 ` Anthony Liguori
2011-03-09 10:20 ` Jes Sorensen
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=4D750A4B.1070304@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).