public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/26076] dlmopen crashes after failing to load dependencies in audit mode Date: Tue, 07 Jul 2020 08:12:11 +0000 [thread overview] Message-ID: <bug-26076-131-yjzciRRJ4o@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26076-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26076 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Target Milestone|--- |2.32 Resolution|--- |FIXED --- Comment #3 from Florian Weimer <fweimer at redhat dot com> --- Fixed for glibc 2.32 with: commit 3ad5dab476205d6e16156cf0511fa6884b3b0fc4 Author: Florian Weimer <fweimer@redhat.com> Date: Tue Jul 7 09:58:45 2020 +0200 elf: Do not signal LA_ACT_CONSISTENT for an empty namespace [BZ #26076] The auditing interface identifies namespaces by their first loaded module. Once the namespace is empty, it is no longer possible to signal LA_ACT_CONSISTENT for it because the first loaded module is already gone at that point. Reviewed-by: Carlos O'Donell <carlos@redhat.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-07 8:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-03 11:43 [Bug dynamic-link/26076] New: dlclose crashes when cleaning up an empty namespace after dlmopen failure fweimer at redhat dot com 2020-06-04 12:50 ` [Bug dynamic-link/26076] dlmopen crashes when cleaning up an empty namespace in audit mode fweimer at redhat dot com 2020-06-04 12:52 ` [Bug dynamic-link/26076] dlmopen crashes after failing to load dependencies " fweimer at redhat dot com 2020-06-04 16:20 ` fweimer at redhat dot com 2020-07-07 8:12 ` fweimer at redhat dot com [this message] 2020-07-07 8:12 ` fweimer at redhat 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-26076-131-yjzciRRJ4o@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: linkBe 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).