From: Jeff Cody <jcody@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kwolf@redhat.com, Markus Armbruster <armbru@redhat.com>,
stefanha@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: do_commit() does not pass along error messages for all errors
Date: Fri, 18 Jan 2013 09:27:40 -0500 [thread overview]
Message-ID: <20130118142740.GA4111@localhost.localdomain> (raw)
In-Reply-To: <20130117095728.60bf72b8@doriath.home>
On Thu, Jan 17, 2013 at 09:57:28AM -0200, Luiz Capitulino wrote:
> On Thu, 17 Jan 2013 08:49:38 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
> > [Cc: Luiz for error stuff]
> >
> > Jeff Cody <jcody@redhat.com> writes:
> >
> > > The non-live bdrv_commit() function may return one of the following
> > > errors: -ENOTSUP, -EBUSY, -EACCES, -EIO. The only error that is
> > > checked in the HMP handler is -EBUSY, so the monitor command 'commit'
> > > silently fails for all error cases other than 'Device is in use'.
> > >
> > > This patch adds the appropriate error messages for the errors
> > > explicitely returned by bdrv_commit().
> > >
> > > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > > ---
> > > blockdev.c | 14 ++++++++++++++
> > > 1 file changed, 14 insertions(+)
> > >
> > > diff --git a/blockdev.c b/blockdev.c
> > > index d724e2d..7db7d8e 100644
> > > --- a/blockdev.c
> > > +++ b/blockdev.c
> > > @@ -657,6 +657,20 @@ void do_commit(Monitor *mon, const QDict *qdict)
> > > qerror_report(QERR_DEVICE_IN_USE, device);
> > > return;
> > > }
> > > + if (ret == -EACCES) {
> > > + qerror_report(QERR_DEVICE_IS_READ_ONLY, device);
> > > + return;
> > > + }
> > > + if (ret == -EIO) {
> > > + qerror_report(QERR_IO_ERROR);
> > > + return;
> > > + }
> > > + if (ret == -ENOTSUP) {
> > > + const char *format = bdrv_get_format_name(bs);
> > > + qerror_report(QERR_BLOCK_FORMAT_FEATURE_NOT_SUPPORTED,
> > > + format ? format : "NULL", device, "commit");
> > > +
> > > + }
> > > }
> > > }
> >
> > A switch could be more obvious than the if cascade. Matter of taste.
> >
> > We're trying to avoid QERR_ in new code. This case isn't bad, because
> > it doesn't add new QERR_ defines. Should we convert the function to
> > error_setg() instead? Perhaps a few cases could be collapsed into a
> > single error_setg_errno() then.
>
> I'd suggest to convert do_commit() to the qapi. However, we already
> have block-commit in QMP. So I'm not sure this is a good idea.
>
> If it isn't, then maybe we could drop all qerro_report() calls and
> use monitor_printf() instead (building the error message with
> strerror()), as do_commit() seems to be used only from HMP.
I think I agree in keeping do_commit() HMP only. I'll submit a v2 to
just use monitor_printf() for all error strings, rather than
qerror_report().
Thanks,
Jeff
prev parent reply other threads:[~2013-01-18 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 23:04 [Qemu-devel] [PATCH] block: do_commit() does not pass along error messages for all errors Jeff Cody
2013-01-17 7:49 ` Markus Armbruster
2013-01-17 11:57 ` Luiz Capitulino
2013-01-18 14:27 ` Jeff Cody [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=20130118142740.GA4111@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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).