qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: "Warner Losh" <imp@bsdimp.com>,
	"Riku Voipio" <riku.voipio@iki.fi>,
	"Laurent Vivier" <laurent@vivier.eu>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Kyle Evans" <kevans@freebsd.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/8] gdbstub: Try unlinking the unix socket before binding
Date: Wed, 08 Jan 2025 16:10:08 +0000	[thread overview]
Message-ID: <875xmpb82n.fsf@draig.linaro.org> (raw)
In-Reply-To: <20241216123412.77450-3-iii@linux.ibm.com> (Ilya Leoshkevich's message of "Mon, 16 Dec 2024 13:33:20 +0100")

Ilya Leoshkevich <iii@linux.ibm.com> writes:

> In case an emulated process execve()s another emulated process, bind()
> will fail, because the socket already exists. So try deleting it.
>
> Note that it is not possible to handle this in do_execv(): deleting
> gdbserver_user_state.socket_path before safe_execve() is not correct,
> because the latter may fail, and afterwards we may lose control.
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
>  gdbstub/user.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gdbstub/user.c b/gdbstub/user.c
> index ef52f249ce9..c900d0a52fe 100644
> --- a/gdbstub/user.c
> +++ b/gdbstub/user.c
> @@ -337,6 +337,7 @@ static int gdbserver_open_socket(const char *path)
>  
>      sockaddr.sun_family = AF_UNIX;
>      pstrcpy(sockaddr.sun_path, sizeof(sockaddr.sun_path) - 1, path);
> +    unlink(sockaddr.sun_path);

Should we be checking for errors here? What do we expect when attempting
to unlink a non-existent path? -EIO?

>      ret = bind(fd, (struct sockaddr *)&sockaddr, sizeof(sockaddr));
>      if (ret < 0) {
>          perror("bind socket");

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2025-01-08 16:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 12:33 [PATCH v3 0/8] gdbstub: Allow late attachment Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 1/8] gdbstub: Allow the %d placeholder in the socket path Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 2/8] gdbstub: Try unlinking the unix socket before binding Ilya Leoshkevich
2025-01-08 16:10   ` Alex Bennée [this message]
2025-01-08 16:14     ` Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 3/8] user: Introduce user/signal.h Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 4/8] user: Introduce host_interrupt_signal Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 5/8] osdep: Introduce qemu_kill_thread() Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 6/8] gdbstub: Allow late attachment Ilya Leoshkevich
2025-01-08 17:20   ` Alex Bennée
2025-01-08 19:48     ` Ilya Leoshkevich
2024-12-16 12:33 ` [PATCH v3 7/8] docs/user: Document the %d placeholder and suspend=n QEMU_GDB features Ilya Leoshkevich
2025-01-08 17:21   ` Alex Bennée
2024-12-16 12:33 ` [PATCH v3 8/8] tests/tcg: Add late gdbstub attach test Ilya Leoshkevich
2025-01-08 17:22   ` Alex Bennée

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=875xmpb82n.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=iii@linux.ibm.com \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --cc=laurent@vivier.eu \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=riku.voipio@iki.fi \
    /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).