From: Luiz Capitulino <lcapitulino@redhat.com>
To: supriya kannery <supriyak@in.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Supriya Kannery <supriyak@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [v9 Patch 2/6]Qemu: Error classes for file reopen and data sync failure
Date: Fri, 18 Nov 2011 10:09:14 -0200 [thread overview]
Message-ID: <20111118100914.20daacee@doriath> (raw)
In-Reply-To: <4EC62584.70403@in.ibm.com>
On Fri, 18 Nov 2011 14:59:40 +0530
supriya kannery <supriyak@in.ibm.com> wrote:
> Luiz Capitulino wrote:
> > On Fri, 11 Nov 2011 12:17:35 +0530
> > Supriya Kannery <supriyak@linux.vnet.ibm.com> wrote:
> >
> >
> >> New error classes defined for file reopen failure and data
> >> sync error
> >>
> >> Signed-off-by: Supriya Kannery <supriyak@linux.vnet.ibm.com>
> >>
> >> ---
> >> qerror.c | 8 ++++++++
> >> qerror.h | 6 ++++++
> >> 2 files changed, 14 insertions(+)
> >>
> >> Index: qemu/qerror.c
> >> ===================================================================
> >> --- qemu.orig/qerror.c
> >> +++ qemu/qerror.c
> >> @@ -97,6 +97,14 @@ static const QErrorStringTable qerror_ta
> >> .desc = "Device '%(device)' is not removable",
> >> },
> >> {
> >> + .error_fmt = QERR_DATA_SYNC_FAILED,
> >> + .desc = "Syncing of data failed for device '%(device)'",
> >> + },
> >> + {
> >> + .error_fmt = QERR_REOPEN_FILE_FAILED,
> >> + .desc = "Could not reopen '%(filename)'",
> >> + },
> >>
> >
> > Is this really needed? I think you could use QERR_OPEN_FILE_FAILED.
> >
> >
>
> This could confuse the user, as to what was tried on an
> already opened file by qemu. So I feel, QERR_REOPEN_FILE_FAILED can
> bring in better clarity to the message passed to the user.
I think it's the contrary.
First, the fact that we reopen the image is an implementation detail. If we
do it differently in the future than the error won't fit anymore.
Second, what did really fail when REOPEN_FILE_FAILED is triggered? Flushing
the buffers? Closing the image? Opening it with different flags? All these
operations are part of the "reopen" algorithm.
On the other hand, if you see a OPEN_FILE_FAILED then there's only one
single operation that might have failed. Also, OPEN_FILE_FAILED is widely
well known as some version of it exists in any operating system.
next prev parent reply other threads:[~2011-11-18 12:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 6:47 [Qemu-devel] [v9 Patch 0/6]Qemu: Host pagecache setting from cmdline and monitor Supriya Kannery
2011-11-11 6:47 ` [Qemu-devel] [v9 Patch 1/6]Qemu: Enhance "info block" to display host cache setting Supriya Kannery
2011-11-11 10:09 ` [Qemu-devel] [v9 Patch 1/6 - updated]Qemu: " Supriya Kannery
2011-11-17 12:38 ` Luiz Capitulino
2011-11-18 9:14 ` supriya kannery
2011-11-11 6:47 ` [Qemu-devel] [v9 Patch 2/6]Qemu: Error classes for file reopen and data sync failure Supriya Kannery
2011-11-17 12:50 ` Luiz Capitulino
2011-11-18 9:29 ` supriya kannery
2011-11-18 12:09 ` Luiz Capitulino [this message]
2011-11-11 6:47 ` [Qemu-devel] [v9 Patch 3/6]Qemu: Cmd "block_set_hostcache" for dynamic cache change Supriya Kannery
2011-11-16 18:34 ` Stefan Hajnoczi
2011-11-17 5:45 ` Supriya Kannery
2011-11-17 13:14 ` Luiz Capitulino
2011-11-17 13:11 ` Luiz Capitulino
2011-11-18 10:44 ` supriya kannery
2011-11-11 6:48 ` [Qemu-devel] [v9 Patch 4/6]Qemu: Add commandline -drive option 'hostcache' Supriya Kannery
2011-11-16 20:06 ` Stefan Hajnoczi
2011-11-17 5:18 ` Supriya Kannery
2011-11-17 14:11 ` Stefan Hajnoczi
2011-11-21 12:28 ` supriya kannery
2011-11-21 14:03 ` Stefan Hajnoczi
2011-11-22 8:10 ` supriya kannery
2011-11-22 9:55 ` Kevin Wolf
2011-11-22 11:17 ` Stefan Hajnoczi
2011-11-22 11:31 ` Kevin Wolf
2011-11-11 6:48 ` [Qemu-devel] [v9 Patch 5/6]Qemu: Framework for reopening images safely Supriya Kannery
2011-11-17 13:16 ` Luiz Capitulino
2011-11-17 14:36 ` Stefan Hajnoczi
2011-11-21 12:13 ` supriya kannery
2011-11-21 14:31 ` Stefan Hajnoczi
2011-11-22 10:24 ` supriya kannery
2011-11-22 11:04 ` Kevin Wolf
2011-11-22 11:16 ` supriya kannery
2011-11-22 11:49 ` Stefan Hajnoczi
2011-11-23 3:52 ` Supriya Kannery
2011-11-11 6:48 ` [Qemu-devel] [v9 Patch 6/6]Qemu: raw posix implementation of reopen functions Supriya Kannery
2011-11-17 14:41 ` Stefan Hajnoczi
2011-11-21 12:30 ` supriya kannery
2011-11-22 9:45 ` supriya kannery
2011-11-22 11:32 ` Stefan Hajnoczi
2011-11-22 11:30 ` supriya kannery
2011-11-22 11:54 ` Stefan Hajnoczi
2011-11-22 11:36 ` Christoph Hellwig
2012-01-19 16:24 ` [Qemu-devel] [v9 Patch 0/6]Qemu: Host pagecache setting from cmdline and monitor 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=20111118100914.20daacee@doriath \
--to=lcapitulino@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=supriyak@in.ibm.com \
--cc=supriyak@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).