From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Michael Tokarev" <mjt@tls.msk.ru>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [RFC PATCH] util: split unix socket functions out of qemu-sockets
Date: Thu, 22 May 2025 15:36:44 +0100 [thread overview]
Message-ID: <659b49bc31ca4f3d9572f9d48e7d09b0@linux.ibm.com> (raw)
In-Reply-To: <20250520165706.3976971-1-alex.bennee@linaro.org>
Thanks for looking into this!
On 2025-05-20 17:57, Alex Bennée wrote:
> Since fccb744f41 (gdbstub: Try unlinking the unix socket before
> binding) we use the unix_listen() function from linux-user which
> causes complications when trying to build statically.
Should this be in Fixes: tag?
> Fix this by splitting the unix functions into its own file and doing
> the appropriate tweaks to the headers.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Reported-by: Michael Tokarev <mjt@tls.msk.ru>
> ---
> include/qemu/sockets.h | 1 +
> util/socket-helpers.h | 17 ++++
> util/qemu-sockets.c | 199 +--------------------------------------
> util/unix-sockets.c | 207 +++++++++++++++++++++++++++++++++++++++++
> util/meson.build | 5 +-
> 5 files changed, 231 insertions(+), 198 deletions(-)
> create mode 100644 util/socket-helpers.h
> create mode 100644 util/unix-sockets.c
[...]
> --- a/util/qemu-sockets.c
> +++ b/util/qemu-sockets.c
> @@ -1,5 +1,5 @@
> /*
> - * inet and unix socket functions for qemu
> + * inet socket functions for qemu
> *
> * (c) 2008 Gerd Hoffmann <kraxel@redhat.com>
> *
Should we mention that static linking of this file is not supported?
With or without this:
Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
prev parent reply other threads:[~2025-05-22 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:57 [RFC PATCH] util: split unix socket functions out of qemu-sockets Alex Bennée
2025-05-21 10:15 ` Daniel P. Berrangé
2025-05-22 14:36 ` Ilya Leoshkevich [this message]
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=659b49bc31ca4f3d9572f9d48e7d09b0@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mjt@tls.msk.ru \
--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).