From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, fam@euphon.net, kwolf@redhat.com,
hreitz@redhat.com, marcandre.lureau@redhat.com,
peterx@redhat.com, farosas@suse.de, pbonzini@redhat.com,
richard.henderson@linaro.org, qemu-block@nongnu.org
Subject: Re: [PATCH 4/6] cpus: Improve error messages on memsave, pmemsave write error
Date: Mon, 27 May 2024 12:41:41 +0200 [thread overview]
Message-ID: <871q5nedui.fsf@pond.sub.org> (raw)
In-Reply-To: <e84312c2-595c-4edc-bd9d-3954a0521ed2@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Mon, 13 May 2024 16:58:11 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 13/5/24 16:45, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>>
>>> On 13/5/24 16:17, Markus Armbruster wrote:
>>>> qmp_memsave() and qmp_pmemsave() report fwrite() error as
>>>>
>>>> An IO error has occurred
>>>>
>>>> Improve this to
>>>>
>>>> writing memory to '<filename>' failed
>>>>
>>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>>> ---
>>>> system/cpus.c | 6 ++++--
>>>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/system/cpus.c b/system/cpus.c
>>>> index 68d161d96b..f8fa78f33d 100644
>>>> --- a/system/cpus.c
>>>> +++ b/system/cpus.c
>>>> @@ -813,7 +813,8 @@ void qmp_memsave(int64_t addr, int64_t size, const char *filename,
>>>> goto exit;
>>>> }
>>>> if (fwrite(buf, 1, l, f) != l) {
>>>> - error_setg(errp, QERR_IO_ERROR);
>>>> + error_setg(errp, "writing memory to '%s' failed",
>>>> + filename);
>>>> goto exit;
>>>> }
>>>> addr += l;
>>>> @@ -843,7 +844,8 @@ void qmp_pmemsave(int64_t addr, int64_t size, const char *filename,
>>>> l = size;
>>>> cpu_physical_memory_read(addr, buf, l);
>>>> if (fwrite(buf, 1, l, f) != l) {
>>>> - error_setg(errp, QERR_IO_ERROR);
>>>> + error_setg(errp, "writing memory to '%s' failed",
>>>> + filename);
>>>
>>> What about including errno with error_setg_errno()?
>>
>> Sure fwrite() fails with errno reliably set? The manual page doesn't
>> mention it...
>
> Indeed. I can see some uses in the code base:
>
> qemu-io-cmds.c:409: if (ferror(f)) {
> qemu-io-cmds.c-410- perror(file_name);
This is after fread(), which isn't specified to set errno, either.
> qga/commands-posix.c-632- write_count = fwrite(buf, 1, count, fh);
> qga/commands-posix.c:633: if (ferror(fh)) {
> qga/commands-posix.c-634- error_setg_errno(errp, errno, "failed to write to file");
This one is after fwrite(), like the code I'm changing.
> util/qemu-config.c:152: if (ferror(fp)) {
> util/qemu-config.c-153- loc_pop(&loc);
> util/qemu-config.c-154- error_setg_errno(errp, errno, "Cannot read config file");
This is after fgets(), which isn't specified to set errno, either.
All three uses feel iffy to me. They work if the stream's error
indicator is clear before fread() / fwrite() / fgets(), and it is set
there, and the reason for it being set is something that sets errno
(such as a failed system call, which seems likely), and errno remains
untouched until after ferror(). Too much "if", "seems likely" for my
taste.
> Regardless,
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Thanks!
next prev parent reply other threads:[~2024-05-27 10:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 14:16 [PATCH 0/6] error: Eliminate QERR_IO_ERROR Markus Armbruster
2024-05-13 14:16 ` [PATCH 1/6] block: Improve error message when external snapshot can't flush Markus Armbruster
2024-05-13 14:24 ` Philippe Mathieu-Daudé
2024-05-13 14:16 ` [PATCH 2/6] dump/win_dump: Improve error messages on write error Markus Armbruster
2024-05-13 14:22 ` Philippe Mathieu-Daudé
2024-05-13 14:48 ` Markus Armbruster
2024-05-13 14:55 ` Philippe Mathieu-Daudé
2024-05-13 14:17 ` [PATCH 3/6] block/vmdk: Improve error messages on extent " Markus Armbruster
2024-05-13 14:23 ` Philippe Mathieu-Daudé
2024-05-13 14:17 ` [PATCH 4/6] cpus: Improve error messages on memsave, pmemsave " Markus Armbruster
2024-05-13 14:27 ` Philippe Mathieu-Daudé
2024-05-13 14:45 ` Markus Armbruster
2024-05-13 14:58 ` Philippe Mathieu-Daudé
2024-05-27 10:41 ` Markus Armbruster [this message]
2024-05-13 14:17 ` [PATCH 5/6] migration: Rephrase message on failure to save / load Xen device state Markus Armbruster
2024-05-13 14:24 ` Philippe Mathieu-Daudé
2024-05-13 18:07 ` Fabiano Rosas
2024-05-23 19:43 ` Peter Xu
2024-05-27 10:53 ` Markus Armbruster
2024-05-27 14:35 ` Peter Xu
2024-05-13 14:17 ` [PATCH 6/6] qerror: QERR_IO_ERROR is no longer used, drop Markus Armbruster
2024-05-13 14:28 ` Philippe Mathieu-Daudé
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=871q5nedui.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).