From: Florian Weimer <fw@deneb.enyo.de>
To: "Wendeborn\, Jonathan via Libc-help" <libc-help@sourceware.org>
Subject: Re: dlopen: Segfault due to overwriting .so file after it was loaded and loading it again
Date: Fri, 20 Nov 2020 12:33:13 +0100 [thread overview]
Message-ID: <87lfewl0ue.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <11e3703d900d48149d0f81ae7682480f@bruexc101.brumgt.local> (Jonathan via Libc-help Wendeborn's message of "Fri, 20 Nov 2020 06:52:35 +0000")
* Jonathan via Libc-help Wendeborn:
> The destructor ~shared_library() calls dlclose(), but I suspect the
> library stays loaded. Overwriting the file creates a new file node
> and my program wants to load the same library again (at the same
> location but with a different file node/handle).
This crash happens if the file is truncated on disk and rewritten.
All mapped data is reset to zero if that happens and relocations are
gone. The kernel does that, there is nothing that glibc can do about
it (Linux does not support MAP_COPY).
So you have two issues here: The library stays loaded (maybe it is
marked as NODELETE, LD_DEBUG=all output logs that in recent glibc
versions), and the file is rewritten in place (and not a “new file
node” is created).
next prev parent reply other threads:[~2020-11-20 11:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 6:52 Wendeborn, Jonathan
2020-11-20 7:17 ` Konstantin Kharlamov
2020-11-20 8:01 ` AW: " Wendeborn, Jonathan
2020-11-20 8:15 ` Konstantin Kharlamov
2020-11-20 9:47 ` AW: " Wendeborn, Jonathan
2020-11-20 10:20 ` Konstantin Kharlamov
2020-11-20 11:33 ` Florian Weimer [this message]
2020-11-20 12:45 ` Wendeborn, Jonathan
2020-11-20 12:48 ` Florian Weimer
2020-11-20 12:59 ` AW: " Wendeborn, Jonathan
2020-12-04 10:39 Wendeborn, Jonathan
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=87lfewl0ue.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-help@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).