From: Carlos O'Donell <carlos@redhat.com>
To: Libc-stable Mailing List <libc-stable@sourceware.org>
Subject: [2.24 COMMITTED] Bug 11941: ld.so: Improper assert map->l_init_called in dlclose
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <35f3bd4a-401b-eb0d-adca-d96e08c14402@redhat.com> (raw)
We are seeing this in Fedora 25 based on glibc 2.24, and it is impacting
kerberos authentication for ssh.
commit a0cd7851a79cccf6e8e21962862ea8fe0bca5114
Author: Carlos O'Donell <carlos@redhat.com>
Date: Fri Dec 23 13:30:22 2016 -0500
Bug 11941: ld.so: Improper assert map->l_init_called in dlclose
There is at least one use case where during exit a library destructor
might call dlclose() on a valid handle and have it fail with an
assertion. We must allow this case, it is a valid handle, and dlclose()
should not fail with an assert. In the future we might be able to return
an error that the dlclose() could not be completed because the opened
library has already been unloaded and destructors have run as part of
exit processing.
For more details see:
https://www.sourceware.org/ml/libc-alpha/2016-12/msg00859.html
(cherry picked from commit 57707b7fcc38855869321f8c7827bfe21d729f37)
--
Cheers,
Carlos.
reply other threads:[~2016-12-23 20:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=35f3bd4a-401b-eb0d-adca-d96e08c14402@redhat.com \
--to=carlos@redhat.com \
--cc=libc-stable@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).