qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/9] QMP/HMP: add error reason to open failures
Date: Mon, 10 Jun 2013 13:02:19 -0400	[thread overview]
Message-ID: <1370883748-31439-1-git-send-email-lcapitulino@redhat.com> (raw)

I was surprised to find out that we still have old users of
QERR_OPEN_FILE_FAILED that print errors like:

(qemu) dump-guest-memory -p /lkmads/foo
Could not open '/lkmads/foo'
(qemu)

This series converts all those users to a new helper called
error_setg_file_open(), which adds error reason to open failures:

(qemu) dump-guest-memory -p /sfmdkjf/foo
Could not open '/sfmdkjf/foo': No such file or directory
(qemu) 

v2

 - bdrv_reopen_prepare(): use generic error message
 - s/error/-ret for bdrv_open() errors

Luiz Capitulino (9):
  error: add error_setg_file_open() helper
  rng-random: use error_setg_file_open()
  block: mirror_complete(): use error_setg_file_open()
  blockdev: use error_setg_file_open()
  cpus: use error_setg_file_open()
  dump: qmp_dump_guest_memory(): use error_setg_file_open()
  savevm: qmp_xen_save_devices_state(): use error_setg_file_open()
  block: bdrv_reopen_prepare(): don't use QERR_OPEN_FILE_FAILED
  qerror: drop QERR_OPEN_FILE_FAILED macro

 backends/rng-random.c     |  3 +--
 block.c                   |  4 ++--
 block/mirror.c            |  2 +-
 blockdev.c                | 11 +++++++----
 cpus.c                    |  4 ++--
 dump.c                    |  2 +-
 include/qapi/error.h      |  5 +++++
 include/qapi/qmp/qerror.h |  3 ---
 savevm.c                  |  2 +-
 util/error.c              |  5 +++++
 10 files changed, 25 insertions(+), 16 deletions(-)

-- 
1.8.1.4

             reply	other threads:[~2013-06-10 17:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 17:02 Luiz Capitulino [this message]
2013-06-10 17:02 ` [Qemu-devel] [PATCH 1/9] error: add error_setg_file_open() helper Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 2/9] rng-random: use error_setg_file_open() Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 3/9] block: mirror_complete(): " Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 4/9] blockdev: " Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 5/9] cpus: " Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 6/9] dump: qmp_dump_guest_memory(): " Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 7/9] savevm: qmp_xen_save_devices_state(): " Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 8/9] block: bdrv_reopen_prepare(): don't use QERR_OPEN_FILE_FAILED Luiz Capitulino
2013-06-11  8:38   ` Kevin Wolf
2013-06-11 12:32     ` Luiz Capitulino
2013-06-10 17:02 ` [Qemu-devel] [PATCH 9/9] qerror: drop QERR_OPEN_FILE_FAILED macro Luiz Capitulino
2013-06-11  7:43 ` [Qemu-devel] [PATCH v2 0/9] QMP/HMP: add error reason to open failures Stefan Hajnoczi
2013-06-11  7:44 ` Stefan Hajnoczi
2013-06-11 12:29   ` Luiz Capitulino
2013-06-11  8:40 ` 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=1370883748-31439-1-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@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).