From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 08/12] util/oslib-win32: Do not treat null @errp as &error_warn
Date: Wed, 17 Sep 2025 13:33:53 -0700 [thread overview]
Message-ID: <7743993b-7ad8-4fe2-a80b-6a40a4fa8360@linaro.org> (raw)
In-Reply-To: <20250917115207.1730186-9-armbru@redhat.com>
On 9/17/25 04:52, Markus Armbruster wrote:
> qemu_socket_select() and its wrapper qemu_socket_unselect() treat a
> null @errp as &error_warn. This is wildly inappropriate. A caller
> passing null @errp specifies that errors are to be ignored. If
> warnings are wanted, the caller must pass &error_warn.
>
> Change callers to do that, and drop the inappropriate treatment of
> null @errp.
>
> This assumes that warnings are wanted. I'm not familiar with the
> calling code, so I can't say whether it will work when the socket is
> invalid, or WSAEventSelect() fails. If it doesn't, then this should
> be an error instead of a warning. Invalid socket might even be a
> programming error.
>
> These warnings were introduced in commit f5fd677ae7cf (win32/socket:
> introduce qemu_socket_select() helper). I considered reverting to
> silence, but Daniel Berrangé asked for the warnings to be preserved.
>
> Cc: Marc-André Lureau<marcandre.lureau@redhat.com>
> Signed-off-by: Markus Armbruster<armbru@redhat.com>
> ---
> io/channel-socket.c | 4 ++--
> io/channel-watch.c | 2 +-
> util/aio-win32.c | 2 +-
> util/oslib-win32.c | 7 ++-----
> 4 files changed, 6 insertions(+), 9 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2025-09-17 20:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 11:51 [PATCH v2 00/12] Error reporting cleanup, a fix, and &error_warn removal Markus Armbruster
2025-09-17 11:51 ` [PATCH v2 01/12] monitor: Clean up HMP gdbserver error reporting Markus Armbruster
2025-09-17 11:51 ` [PATCH v2 02/12] tcg: Fix error reporting on mprotect() failure in tcg_region_init() Markus Armbruster
2025-09-17 16:23 ` Richard Henderson
2025-09-18 12:23 ` Akihiko Odaki
2025-09-18 14:22 ` Markus Armbruster
2025-09-17 11:51 ` [PATCH v2 03/12] hw/cxl: Convert cxl_fmws_link() to Error Markus Armbruster
2025-09-17 13:15 ` Jonathan Cameron via
2025-09-17 11:51 ` [PATCH v2 04/12] migration/cpr: Clean up error reporting in cpr_resave_fd() Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 05/12] hw/remote/vfio-user: Clean up error reporting Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 06/12] net/slirp: " Markus Armbruster
2025-09-18 12:24 ` Akihiko Odaki
2025-09-18 14:24 ` Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 07/12] ui/spice-core: " Markus Armbruster
2025-09-17 20:34 ` Richard Henderson
2025-09-17 11:52 ` [PATCH v2 08/12] util/oslib-win32: Do not treat null @errp as &error_warn Markus Armbruster
2025-09-17 20:33 ` Richard Henderson [this message]
2025-09-17 11:52 ` [PATCH v2 09/12] ui/pixman: Consistent error handling in qemu_pixman_shareable_free() Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 10/12] ui/dbus: Clean up dbus_update_gl_cb() error checking Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 11/12] ui/dbus: Consistent handling of texture mutex failure Markus Armbruster
2025-09-17 11:52 ` [PATCH v2 12/12] error: Kill @error_warn Markus Armbruster
2025-09-17 15:18 ` Vladimir Sementsov-Ogievskiy
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=7743993b-7ad8-4fe2-a80b-6a40a4fa8360@linaro.org \
--to=richard.henderson@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 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).