From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Cole Robinson <crobinso@redhat.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
dgilbert@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-4.0?] hmp: delvm: use hmp_handle_error
Date: Fri, 12 Apr 2019 14:21:33 +0200 [thread overview]
Message-ID: <20190412122133.GG4522@linux.fritz.box> (raw)
In-Reply-To: <4aee66fd-1cfa-a935-daa6-6f221af42095@redhat.com>
Am 10.04.2019 um 20:27 hat Eric Blake geschrieben:
> On 4/10/19 1:03 PM, Cole Robinson wrote:
> > This gives us the consistent 'Error:' prefix added in 66363e9a43f,
> > which helps users like libvirt who still need to scrape hmp error
> > messages to detect failure.
> >
> > Signed-off-by: Cole Robinson <crobinso@redhat.com>
> > ---
> > hmp.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
>
> Not enough to drive -rc4 on its own, but worth adding to our wishlist of
> potential easy patches if we do have a release blocker surface.
As we are going to have an -rc4, I had a look at this.
Commit 66363e9a43f was in February and explicitly says "Note: Some
places don't use hmp_handle_error". So this doesn't seem to be a
regression and even if it's fixed, it's likely not the last place that
doesn't use the "Error:" prefix. This would suggest that this isn't for
-rc4.
Am I misunderstanding the situation?
Kevin
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> >
> > diff --git a/hmp.c b/hmp.c
> > index 8eec768088..74a4bfc1f9 100644
> > --- a/hmp.c
> > +++ b/hmp.c
> > @@ -1481,10 +1481,11 @@ void hmp_delvm(Monitor *mon, const QDict *qdict)
> > const char *name = qdict_get_str(qdict, "name");
> >
> > if (bdrv_all_delete_snapshot(name, &bs, &err) < 0) {
> > - error_reportf_err(err,
> > - "Error while deleting snapshot on device '%s': ",
> > - bdrv_get_device_name(bs));
> > + error_prepend(&err,
> > + "Error while deleting snapshot on device '%s': ",
>
> Do we want to reword the message (maybe s/Error while //) to avoid the
> word "Error" twice in the same line?
>
> > + bdrv_get_device_name(bs));
> > }
> > + hmp_handle_error(mon, &err);
> > }
> >
> > void hmp_info_snapshots(Monitor *mon, const QDict *qdict)
> >
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3226
> Virtualization: qemu.org | libvirt.org
>
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, dgilbert@redhat.com,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0?] hmp: delvm: use hmp_handle_error
Date: Fri, 12 Apr 2019 14:21:33 +0200 [thread overview]
Message-ID: <20190412122133.GG4522@linux.fritz.box> (raw)
Message-ID: <20190412122133.jVt7oCHSoO9Ibv_T6ykMNhNgSYupz6SzjjoGPfEQXJQ@z> (raw)
In-Reply-To: <4aee66fd-1cfa-a935-daa6-6f221af42095@redhat.com>
Am 10.04.2019 um 20:27 hat Eric Blake geschrieben:
> On 4/10/19 1:03 PM, Cole Robinson wrote:
> > This gives us the consistent 'Error:' prefix added in 66363e9a43f,
> > which helps users like libvirt who still need to scrape hmp error
> > messages to detect failure.
> >
> > Signed-off-by: Cole Robinson <crobinso@redhat.com>
> > ---
> > hmp.c | 7 ++++---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
>
> Not enough to drive -rc4 on its own, but worth adding to our wishlist of
> potential easy patches if we do have a release blocker surface.
As we are going to have an -rc4, I had a look at this.
Commit 66363e9a43f was in February and explicitly says "Note: Some
places don't use hmp_handle_error". So this doesn't seem to be a
regression and even if it's fixed, it's likely not the last place that
doesn't use the "Error:" prefix. This would suggest that this isn't for
-rc4.
Am I misunderstanding the situation?
Kevin
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> >
> > diff --git a/hmp.c b/hmp.c
> > index 8eec768088..74a4bfc1f9 100644
> > --- a/hmp.c
> > +++ b/hmp.c
> > @@ -1481,10 +1481,11 @@ void hmp_delvm(Monitor *mon, const QDict *qdict)
> > const char *name = qdict_get_str(qdict, "name");
> >
> > if (bdrv_all_delete_snapshot(name, &bs, &err) < 0) {
> > - error_reportf_err(err,
> > - "Error while deleting snapshot on device '%s': ",
> > - bdrv_get_device_name(bs));
> > + error_prepend(&err,
> > + "Error while deleting snapshot on device '%s': ",
>
> Do we want to reword the message (maybe s/Error while //) to avoid the
> word "Error" twice in the same line?
>
> > + bdrv_get_device_name(bs));
> > }
> > + hmp_handle_error(mon, &err);
> > }
> >
> > void hmp_info_snapshots(Monitor *mon, const QDict *qdict)
> >
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3226
> Virtualization: qemu.org | libvirt.org
>
next prev parent reply other threads:[~2019-04-12 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 18:03 [Qemu-devel] [PATCH] hmp: delvm: use hmp_handle_error Cole Robinson
2019-04-10 18:27 ` [Qemu-devel] [PATCH for-4.0?] " Eric Blake
2019-04-10 18:27 ` Eric Blake
2019-04-10 18:36 ` Cole Robinson
2019-04-10 18:36 ` Cole Robinson
2019-04-12 12:21 ` Kevin Wolf [this message]
2019-04-12 12:21 ` Kevin Wolf
2019-04-12 14:55 ` Eric Blake
2019-04-12 14:55 ` Eric Blake
2019-04-12 18:12 ` Cole Robinson
2019-04-12 18:12 ` Cole Robinson
2019-04-12 18:15 ` [Qemu-devel] [PATCH] " Markus Armbruster
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=20190412122133.GG4522@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=crobinso@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.