From: mdroth <mdroth@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 03/10] qemu-ga: qmp_guest_file_*: improve error reporting
Date: Wed, 28 Nov 2012 11:54:45 -0600 [thread overview]
Message-ID: <20121128175445.GE8690@vm> (raw)
In-Reply-To: <1354021324-31561-4-git-send-email-lcapitulino@redhat.com>
On Tue, Nov 27, 2012 at 11:01:57AM -0200, Luiz Capitulino wrote:
> Use error_setg_errno() when possible with an improved error description.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> qga/commands-posix.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index c284083..92fc550 100644
> --- a/qga/commands-posix.c
> +++ b/qga/commands-posix.c
> @@ -138,7 +138,8 @@ int64_t qmp_guest_file_open(const char *path, bool has_mode, const char *mode, E
> slog("guest-file-open called, filepath: %s, mode: %s", path, mode);
> fh = fopen(path, mode);
> if (!fh) {
> - error_set(err, QERR_OPEN_FILE_FAILED, path);
> + error_setg_errno(err, errno, "failed to open file '%s' (mode: '%s')",
> + path, mode);
> return -1;
> }
>
> @@ -149,7 +150,8 @@ int64_t qmp_guest_file_open(const char *path, bool has_mode, const char *mode, E
> ret = fcntl(fd, F_GETFL);
> ret = fcntl(fd, F_SETFL, ret | O_NONBLOCK);
> if (ret == -1) {
> - error_set(err, QERR_QGA_COMMAND_FAILED, "fcntl() failed");
> + error_setg_errno(err, errno, "failed to make file '%s' non-blocking",
> + path);
> fclose(fh);
> return -1;
> }
> @@ -171,7 +173,7 @@ void qmp_guest_file_close(int64_t handle, Error **err)
>
> ret = fclose(gfh->fh);
> if (ret == EOF) {
> - error_set(err, QERR_QGA_COMMAND_FAILED, "fclose() failed");
> + error_setg_errno(err, errno, "failed to close handle");
> return;
> }
>
> @@ -195,7 +197,8 @@ struct GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
> if (!has_count) {
> count = QGA_READ_COUNT_DEFAULT;
> } else if (count < 0) {
> - error_set(err, QERR_INVALID_PARAMETER, "count");
> + error_setg(err, "value '%" PRId64 "' is invalid for argument count",
> + count);
> return NULL;
> }
>
> @@ -203,8 +206,8 @@ struct GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
> buf = g_malloc0(count+1);
> read_count = fread(buf, 1, count, fh);
> if (ferror(fh)) {
> + error_setg_errno(err, errno, "failed to read file");
> slog("guest-file-read failed, handle: %ld", handle);
> - error_set(err, QERR_QGA_COMMAND_FAILED, "fread() failed");
> } else {
I'm not sure about relying on errno for FILE/f*() functions. C99 doesn't
appear to require setting it for implementations (unfortunately), and
glibc doesn't document it for fwrite/fread (although it does for most others).
I'm guessing it's okay for glibc, but there be cases where we print random
error messages. We can do this portably by setting errno = 0 before the
fread()/f*()s, and using error_setg() if it's still 0 after we detect an
error, but that's pretty nasty.
Unless we can confirm there's aren't any implementations out there we
care about where errno isn't set, maybe we should just stick to
error_setg() for the f* functions? Hate to throw away error messages, but
incorrect/random errors would be worse.
<snip>
next prev parent reply other threads:[~2012-11-28 18:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 13:01 [Qemu-devel] [PATCH 00/10] qemu-ga: revamp error messages (for 1.4) Luiz Capitulino
2012-11-27 13:01 ` [Qemu-devel] [PATCH 01/10] qemu-ga: guest_file_handle_find(): take an Error argument Luiz Capitulino
2012-11-28 17:01 ` mdroth
2012-11-27 13:01 ` [Qemu-devel] [PATCH 02/10] qemu-ga: qmp_guest_file_close(): fix fclose() error check Luiz Capitulino
2012-11-28 17:02 ` mdroth
2012-11-27 13:01 ` [Qemu-devel] [PATCH 03/10] qemu-ga: qmp_guest_file_*: improve error reporting Luiz Capitulino
2012-11-28 17:54 ` mdroth [this message]
2012-11-28 19:31 ` Luiz Capitulino
2012-11-28 21:26 ` Eric Blake
2012-11-28 22:17 ` mdroth
2012-11-29 12:00 ` Luiz Capitulino
2012-11-27 13:01 ` [Qemu-devel] [PATCH 04/10] qemu-ga: qmp_guest_shutdown(): " Luiz Capitulino
2012-11-28 19:27 ` mdroth
2012-11-27 13:01 ` [Qemu-devel] [PATCH 05/10] qemu-ga: build_fs_mount_list(): take an Error argument Luiz Capitulino
2012-11-28 19:34 ` mdroth
2012-11-29 17:29 ` [Qemu-devel] [PATCH v2 " Luiz Capitulino
2012-11-27 13:02 ` [Qemu-devel] [PATCH 06/10] qemu-ga: qmp_guest_fsfreeze_*(): get rid of sprintf() + error_set() Luiz Capitulino
2012-11-28 19:40 ` mdroth
2012-11-27 13:02 ` [Qemu-devel] [PATCH 07/10] qemu-ga: qmp_guest_fstrim(): " Luiz Capitulino
2012-11-28 19:41 ` mdroth
2012-11-27 13:02 ` [Qemu-devel] [PATCH 08/10] qemu-ga: qmp_guest_network_get_interfaces(): get rid of snprintf() " Luiz Capitulino
2012-11-28 19:43 ` mdroth
2012-11-27 13:02 ` [Qemu-devel] [PATCH 09/10] qemu-ga: bios_supports_mode(): improve error reporting Luiz Capitulino
2012-11-28 19:48 ` mdroth
2012-11-27 13:02 ` [Qemu-devel] [PATCH 10/10] qemu-ga: guest_suspend(): " Luiz Capitulino
2012-11-28 19:49 ` mdroth
2012-11-28 20:04 ` [Qemu-devel] [PATCH 00/10] qemu-ga: revamp error messages (for 1.4) mdroth
2012-11-28 20:12 ` mdroth
2012-12-12 1:03 ` Eric Blake
2012-11-30 18:22 ` mdroth
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=20121128175445.GE8690@vm \
--to=mdroth@linux.vnet.ibm.com \
--cc=lcapitulino@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).