All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Ilya Leoshkevich" <iii@linux.ibm.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Peter Xu" <peterx@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Weiwei Li" <liwei1518@gmail.com>,
	qemu-arm@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
	"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
	"Bin Meng" <bmeng.cn@gmail.com>,
	"Tyrone Ting" <kfting@nuvoton.com>,
	"Hao Wu" <wuhaotsh@google.com>, "Kyle Evans" <kevans@freebsd.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Laurent Vivier" <laurent@vivier.eu>,
	"Riku Voipio" <riku.voipio@iki.fi>,
	"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Alexandre Iooss" <erdnaxe@crans.org>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Warner Losh" <imp@bsdimp.com>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Mahmoud Mandour" <ma.mandourr@gmail.com>,
	qemu-ppc@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-rust@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH v2 11/17] gdbstub: Try unlinking the unix socket before binding
Date: Wed, 21 May 2025 16:37:51 +0100	[thread overview]
Message-ID: <aC3zT7gOMn4i-d4U@redhat.com> (raw)
In-Reply-To: <CAFEAcA8Mzo-Ne48=uFBTcy+CXNcnxGOaW941p=CRkD6gmC=JfA@mail.gmail.com>

On Wed, May 21, 2025 at 04:34:24PM +0100, Peter Maydell wrote:
> On Tue, 20 May 2025 at 23:22, Ilya Leoshkevich <iii@linux.ibm.com> wrote:
> > However, wasn't it already broken in this regard?
> > With fccb744f41c69fec6fd92225fe907c6e69de5d44^ I get:
> >
> > [2/2] Linking target qemu-s390x
> > /usr/bin/ld: /usr/lib64/libglib-2.0.a(gutils.c.o): in function
> > `g_get_user_database_entry':
> > (.text+0xeb): warning: Using 'getpwnam_r' in statically linked
> > applications requires at runtime the shared libraries from the glibc
> > version used for linking
> > /usr/bin/ld: (.text+0x2be): warning: Using 'getpwuid' in statically
> > linked applications requires at runtime the shared libraries from the
> > glibc version used for linking
> > /usr/bin/ld: (.text+0x134): warning: Using 'getpwuid_r' in statically
> > linked applications requires at runtime the shared libraries from the
> > glibc version used for linking
> >
> > This comes from glib, but the ultimate result is still the same.
> 
> Those are in upstream glib, as you note. We can't fix those (unless we
> have the enthusiasm to write patches for upstream glib: last time
> we asked, they were not against the idea, but nobody on either side
> had the time available to try to write the necessary patches).
> But we can and should fix the cases in our own code.
> 
> > Also, what are the symptoms of the breakage? IIUC as long as execution
> > does not reach getaddrinfo(), which it in this case should not, because
> > it is used only on inet paths, there should not be any issues, right?
> 
> Correct -- if we don't call the function it's fine. But the easiest
> way to be sure we don't call the function is to not link it in :-)
> Otherwise future code changes could result in a call without our
> realizing it.
> 
> Also, mjt's packaging for Debian puts in some stubs for the
> offending getwpuid etc functions, which suppress the glib warnings
> (this is why he noticed this whereas none of the rest of us did):
> 
> https://sources.debian.org/patches/qemu/1:10.0.0%2Bds-2/static-linux-user-stubs.diff/

Oh interesting, I was conincidentally wondering if adding dummy
stubs might suppress this.

How about we pull that change upstream, and expand it to getaddrinfo
too ?  I like the stubs much more than artificially splitting up
the source files


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-05-21 15:38 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-07 15:30 [PATCH v2 00/17] maintainer updates for feb25 (qtest, gdbstub, plugins) pre-PR Alex Bennée
2025-02-07 15:30 ` [PATCH v2 01/17] tests/docker: replicate the check-rust-tools-nightly CI job Alex Bennée
2025-02-07 18:06   ` Richard Henderson
2025-02-07 15:30 ` [PATCH v2 02/17] tests/qtest: don't attempt to clock_step while waiting for virtio ISR Alex Bennée
2025-02-07 16:02   ` Thomas Huth
2025-02-07 15:30 ` [PATCH v2 03/17] tests/qtest: don't step clock at start of npcm7xx periodic IRQ test Alex Bennée
2025-02-07 15:30 ` [PATCH v2 04/17] tests/qtest: simplify qtest_process_inbuf Alex Bennée
2025-02-07 15:31 ` [PATCH v2 05/17] tests/qtest: rename qtest_send_prefix and roll-up into qtest_send Alex Bennée
2025-02-07 16:04   ` Thomas Huth
2025-02-07 15:31 ` [PATCH v2 06/17] tests/qtest: tighten up the checks on clock_step Alex Bennée
2025-02-07 15:31 ` [PATCH v2 07/17] Revert "util/timer: avoid deadlock when shutting down" Alex Bennée
2025-02-07 15:31 ` [PATCH v2 08/17] tests/qtest/migration: Add --full option Alex Bennée
2025-02-07 15:31 ` [PATCH v2 09/17] tests/qtest/migration: Pick smoke tests Alex Bennée
2025-02-07 15:31 ` [PATCH v2 10/17] gdbstub: Allow the %d placeholder in the socket path Alex Bennée
2025-02-07 15:31 ` [PATCH v2 11/17] gdbstub: Try unlinking the unix socket before binding Alex Bennée
2025-05-20 14:50   ` Michael Tokarev
2025-05-20 15:52     ` Alex Bennée
2025-05-20 16:01       ` Peter Maydell
2025-05-20 22:21     ` Ilya Leoshkevich
2025-05-21  6:22       ` Alex Bennée
2025-05-21 15:34       ` Peter Maydell
2025-05-21 15:37         ` Daniel P. Berrangé [this message]
2025-05-21 15:41           ` Peter Maydell
2025-02-07 15:31 ` [PATCH v2 12/17] user: Introduce user/signal.h Alex Bennée
2025-02-07 15:31 ` [PATCH v2 13/17] user: Introduce host_interrupt_signal Alex Bennée
2025-02-07 15:31 ` [PATCH v2 14/17] osdep: Introduce qemu_kill_thread() Alex Bennée
2025-02-07 15:31 ` [PATCH v2 15/17] gdbstub: Allow late attachment Alex Bennée
2025-02-07 15:31 ` [PATCH v2 16/17] docs/user: Document the %d placeholder and suspend=n QEMU_GDB features Alex Bennée
2025-02-07 15:31 ` [PATCH v2 17/17] tests/tcg: Add late gdbstub attach test 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=aC3zT7gOMn4i-d4U@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=bmeng.cn@gmail.com \
    --cc=danielhb413@gmail.com \
    --cc=erdnaxe@crans.org \
    --cc=farosas@suse.de \
    --cc=harshpb@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --cc=kfting@nuvoton.com \
    --cc=laurent@vivier.eu \
    --cc=liwei1518@gmail.com \
    --cc=lvivier@redhat.com \
    --cc=ma.mandourr@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=npiggin@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=qemu-rust@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=thuth@redhat.com \
    --cc=wuhaotsh@google.com \
    --cc=zhiwei_liu@linux.alibaba.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.