From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Adhemerval Zanella Netto via Libc-alpha
<libc-alpha@sourceware.org>,
Joan Bruguera <joanbrugueram@gmail.com>
Subject: Re: [PATCH v4] elf: Restore ldconfig libc6 implicit soname logic [BZ #30125]
Date: Mon, 20 Feb 2023 15:04:39 +0100 [thread overview]
Message-ID: <87wn4cfn60.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <70e98b0f-26c4-82ca-50ce-1efd31102988@linaro.org> (Adhemerval Zanella Netto's message of "Mon, 20 Feb 2023 10:55:53 -0300")
* Adhemerval Zanella Netto:
> On 20/02/23 10:21, Florian Weimer wrote:
>> * Adhemerval Zanella Netto via Libc-alpha:
>>
>>> On 18/02/23 18:52, Joan Bruguera wrote:
>>>> While cleaning up old libc version support, the deprecated libc4 code was
>>>> accidentally kept in `implicit_soname`, instead of the libc6 code.
>>>>
>>>> This causes additional symlinks to be created by `ldconfig` for libraries
>>>> without a soname, e.g. a library `libsomething.123.456.789` without a soname
>>>> will create a `libsomething.123` -> `libsomething.123.456.789` symlink.
>>>>
>>>> As the libc6 version of the `implicit_soname` code is a trivial `xstrdup`,
>>>> just inline it and remove `implicit_soname` altogether.
>>>>
>>>> Some further simplification looks possible (e.g. the call to `create_links`
>>>> looks like a no-op if `soname == NULL`, other than the verbose printfs), but
>>>> logic is kept as-is for now.
>>>>
>>>> Fixes: BZ #30125
>>>> Fixes: 8ee878592c4a ("Assume only FLAG_ELF_LIBC6 suport")
>>>> Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com>
>>>
>>> LGTM, thanks.
>>>
>>> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>>
>> Reviewed-by: Florian Weimer <fweimer@redhat.com>
>>
>> Are you going to push & backport this to glibc 2.37?
>
> I already did from 2.34 to 2.37.
I think this was about a different regression?
commit fd78cfa72ea2bab30fdb4e1e0672b34471426c05
Author: Vitaly Buka <vitalybuka@google.com>
Date: Sat Feb 18 12:53:41 2023 -0800
stdlib: Undo post review change to 16adc58e73f3 [BZ #27749]
Not this one here.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-20 14:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 1:41 [PATCH] elf: Restore lconfig " Joan Bruguera
2023-02-15 1:47 ` Joan Bruguera
2023-02-15 13:19 ` Adhemerval Zanella Netto
2023-02-16 1:29 ` Joan Bruguera
2023-02-16 1:40 ` Sam James
2023-02-16 2:23 ` [PATCH v3] elf: Restore ldconfig " Joan Bruguera
2023-02-16 6:08 ` Florian Weimer
2023-02-16 2:23 ` [PATCH] elf: Restore lconfig " Joan Bruguera
2023-02-16 6:01 ` Florian Weimer
2023-02-16 1:24 ` [PATCH v2] elf: Restore ldconfig " Joan Bruguera
2023-02-16 2:08 ` [PATCH v3] " Joan Bruguera
2023-02-18 21:52 ` [PATCH v4] " Joan Bruguera
2023-02-20 12:32 ` Adhemerval Zanella Netto
2023-02-20 13:21 ` Florian Weimer
2023-02-20 13:55 ` Adhemerval Zanella Netto
2023-02-20 14:04 ` Florian Weimer [this message]
2023-02-20 14:26 ` Adhemerval Zanella Netto
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=87wn4cfn60.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=joanbrugueram@gmail.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).