public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joanbrugueram at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30125] New: [regression, bisected] glibc-2.37 creates new symlink created in for libraries without soname
Date: Wed, 15 Feb 2023 00:22:18 +0000	[thread overview]
Message-ID: <bug-30125-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30125

            Bug ID: 30125
           Summary: [regression, bisected] glibc-2.37 creates new symlink
                    created in for libraries without soname
           Product: glibc
           Version: 2.37
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: joanbrugueram at gmail dot com
  Target Milestone: ---

Since installing glibc-2.37 I have noticed that `ldconfig` creates symlinks it
did not previously create for libraries without a soname.

In particular, if a library is for exmple named `libsomething.so.123.456.789`,
running `ldconfig` will now create a symlink named `libsomething.123` pointing
to `libsomething.123.456.789`, whereas previously it did not create this
symlink.

A complete reproducer is:

    #!/usr/bin/env sh
    set -eu

    rm -rf sonametest
    mkdir -p sonametest/etc sonametest/usr/lib
    gcc /dev/null -o sonametest/usr/lib/libtestsoname.so.123.456.789 -shared

    ldconfig -r sonametest
    ls -l1 sonametest/usr/lib/

Output with glibc-2.36:

    -rwxr-xr-x 1 user user 14520 11. Feb 12:34 libtestsoname.so.123.456.789

Output with glibc-2.37:

    lrwxrwxrwx 1 user user    28 11. Feb 12:34 libtestsoname.so.123 ->
libtestsoname.so.123.456.789
    -rwxr-xr-x 1 user user 14520 11. Feb 12:34 libtestsoname.so.123.456.789

I have bisected the change in behavior to commit
8ee878592c4a642937152c8308b8faef86bcfc40 "Assume only FLAG_ELF_LIBC6 suport".
It appears that the refactor in `implicit_soname` picked the wrong branch of
the `if` so `implicit_soname` now behaves always behaves as it did for libc4
libraries.

The only negative effect I have noticed from this is that unnecessary files are
created on the system.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-02-15  0:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  0:22 joanbrugueram at gmail dot com [this message]
2023-02-15  0:22 ` [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink created " joanbrugueram at gmail dot com
2023-02-15  0:23 ` [Bug dynamic-link/30125] [regression, bisected] glibc-2.37 creates new symlink " joanbrugueram at gmail dot com
2023-02-15  0:23 ` joanbrugueram at gmail dot com
2023-02-15  0:34 ` joanbrugueram at gmail dot com
2023-02-15  9:21 ` sam at gentoo dot org
2023-02-20 12:35 ` cvs-commit at gcc dot gnu.org
2023-02-20 12:36 ` adhemerval.zanella at linaro dot org
2023-02-20 16:32 ` cvs-commit at gcc dot gnu.org

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=bug-30125-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).