From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 14/24] migration: Use error_reportf_err() instead of monitor_printf()
Date: Fri, 18 Dec 2015 16:35:17 +0100 [thread overview]
Message-ID: <1450452927-8346-15-git-send-email-armbru@redhat.com> (raw)
In-Reply-To: <1450452927-8346-1-git-send-email-armbru@redhat.com>
Both error_reportf_err() and monitor_printf() print to the same
destination when monitor_printf() is used correctly, i.e. within an
HMP monitor. Elsewhere, monitor_printf() does nothing, while
error_reportf_err() reports to stderr.
Both changed functions are HMP command handlers. These should only
run within an HMP monitor.
Unlike monitor_printf(), error_reportf_err() uses the error whole
instead of just its message obtained with error_get_pretty(). This
avoids suppressing its hint (see commit 50b7b00), but I don't think
the errors touched in this commit can come with hints.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
migration/savevm.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/migration/savevm.c b/migration/savevm.c
index e277b72..bcaeb70 100644
--- a/migration/savevm.c
+++ b/migration/savevm.c
@@ -1927,10 +1927,9 @@ void hmp_savevm(Monitor *mon, const QDict *qdict)
/* Delete old snapshots of the same name */
if (name && bdrv_all_delete_snapshot(name, &bs1, &local_err) < 0) {
- monitor_printf(mon,
- "Error while deleting snapshot on device '%s': %s\n",
- bdrv_get_device_name(bs1), error_get_pretty(local_err));
- error_free(local_err);
+ error_reportf_err(local_err,
+ "Error while deleting snapshot on device '%s': ",
+ bdrv_get_device_name(bs1));
return;
}
@@ -2108,10 +2107,9 @@ 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) {
- monitor_printf(mon,
- "Error while deleting snapshot on device '%s': %s\n",
- bdrv_get_device_name(bs), error_get_pretty(err));
- error_free(err);
+ error_reportf_err(err,
+ "Error while deleting snapshot on device '%s': ",
+ bdrv_get_device_name(bs));
}
}
--
2.4.3
next prev parent reply other threads:[~2015-12-18 15:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 15:35 [Qemu-devel] [PATCH v3 00/24] Error reporting cleanups and fixes Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 01/24] qemu-nbd: Replace BSDism <err.h> by error_report() Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 02/24] error: Use error_report_err() where appropriate (again) Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 03/24] error: Use error_report_err() instead of monitor_printf() Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 04/24] error: Use error_report_err() instead of ad hoc prints Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 05/24] error: Improve documentation Markus Armbruster
2015-12-18 15:51 ` Eric Blake
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 06/24] block: Clean up "Could not create temporary overlay" error message Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 07/24] qemu-nbd: Clean up "Failed to load snapshot" " Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 08/24] test-throttle: Simplify qemu_init_main_loop() error handling Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 09/24] error: New error_prepend(), error_reportf_err() Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 10/24] error: Don't decorate original error message when adding to it Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 11/24] error: Use error_reportf_err() where it makes obvious sense Markus Armbruster
2015-12-18 16:08 ` Eric Blake
2015-12-18 16:22 ` Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 12/24] error: Use error_prepend() " Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 13/24] spapr: Use error_reportf_err() Markus Armbruster
2015-12-18 15:35 ` Markus Armbruster [this message]
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 15/24] qemu-io qemu-nbd: Use error_report() etc. instead of fprintf() Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 16/24] error: Strip trailing '\n' from error string arguments (again) Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 17/24] vmdk: Clean up control flow in vmdk_parse_extents() a bit Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 18/24] vmdk: Clean up "Invalid extent lines" error message Markus Armbruster
2015-12-22 1:30 ` Fam Zheng
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 19/24] pci-assign: Clean up "Failed to assign" error messages Markus Armbruster
2016-01-04 15:44 ` Laszlo Ersek
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 20/24] vhdx: Fix "log that needs to be replayed" error message Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 21/24] error: Clean up errors with embedded newlines (again) Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 22/24] hw/s390x: Rename local variables Error *l_err to just err Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 23/24] s390/sclp: Simplify control flow in sclp_realize() Markus Armbruster
2015-12-18 15:35 ` [Qemu-devel] [PATCH v3 24/24] error: Consistently name Error * objects err, and not errp Markus Armbruster
2015-12-18 16:11 ` Eric Blake
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=1450452927-8346-15-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--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 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).