public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/31230] New: PLT rewrite failed without SELinux
Date: Thu, 11 Jan 2024 01:58:44 +0000	[thread overview]
Message-ID: <bug-31230-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 31230
           Summary: PLT rewrite failed without SELinux
           Product: glibc
           Version: 2.39
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
  Target Milestone: ---

I backported PLT rewrite to my glibc and added

export GLIBC_TUNABLES=glibc.cpu.plt_rewrite=2

to my shell.  Now I got

Jan 10 17:23:28 gnu-cfl-3 pipewire[2420]: /usr/bin/pipewire: error while
loading shared libraries: /lib64/libc.so.6: failed to change PLT back to
read-only
Jan 10 17:23:28 gnu-cfl-3 wireplumber[2711]: /usr/bin/wireplumber: error while
loading shared libraries: /lib64/libc.so.6: failed to change PLT back to
read-only
Jan 10 17:23:29 gnu-cfl-3 pipewire-pulse[3019]: /usr/bin/pipewire-pulse: error
while loading shared libraries: /lib64/libc.so.6: failed to change PLT back to
read-only

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

             reply	other threads:[~2024-01-11  1:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  1:58 hjl.tools at gmail dot com [this message]
2024-01-11  9:41 ` [Bug dynamic-link/31230] " sam at gentoo dot org
2024-01-11 14:15 ` hjl.tools at gmail dot com
2024-01-15 14:59 ` cvs-commit at gcc dot gnu.org
2024-01-15 15:12 ` hjl.tools at gmail dot com

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-31230-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).