From: Kevin Wolf <kwolf@redhat.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Re: [PATCH v2] Improve error handling in do_snapshot_blkdev()
Date: Mon, 07 Mar 2011 16:31:08 +0100 [thread overview]
Message-ID: <4D74FA3C.1010205@redhat.com> (raw)
In-Reply-To: <4D74F8AE.8000205@redhat.com>
Am 07.03.2011 16:24, schrieb Jes Sorensen:
> On 03/07/11 11:01, Kevin Wolf wrote:
>> Am 03.03.2011 14:13, schrieb Jes.Sorensen@redhat.com:
>>> @@ -591,6 +592,12 @@ int do_snapshot_blkdev(Monitor *mon, const QDict *qdict, QObject **ret_data)
>>> goto out;
>>> }
>>>
>>> + strncpy(old_filename, bs->filename, sizeof(old_filename));
>>> + old_filename[1023] = '\0';
>>
>> qemu has pstrcpy() from cutils.c for this.
>
> I'll change it to use pstrcpy().
>
>>> - 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",
>>
>> That should probably be a colon in "%s: Attempting..." Also, is the
>> leading space intentional?
>
> The colon is already there prior to the \n" on the previous printf line.
> The space was intentional, but maybe that will just confuse people so I
> will remove it. I added a colon after image: in the last line instead.
Sorry, I failed to read the context. It's the end of a sentence started
in the line before, so having . instead of : after %s is correct, of course.
Kevin
prev parent reply other threads:[~2011-03-07 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 13:13 [Qemu-devel] [PATCH v2] Improve error handling in do_snapshot_blkdev() Jes.Sorensen
2011-03-03 13:18 ` [Qemu-devel] " Stefan Hajnoczi
2011-03-07 10:01 ` Kevin Wolf
2011-03-07 15:24 ` Jes Sorensen
2011-03-07 15:31 ` Kevin Wolf [this message]
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=4D74FA3C.1010205@redhat.com \
--to=kwolf@redhat.com \
--cc=Jes.Sorensen@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).