From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Richard Henderson <rth@redhat.com>,
Szabolcs Nagy <nsz@port70.net>,
GNU C Library <libc-alpha@sourceware.org>,
Roland McGrath <roland@hack.frob.com>
Subject: Re: Incorrect IFUNC use in libpthread for fork, vfork wrapper [BZ #19861]
Date: Mon, 11 Apr 2016 10:02:00 -0000 [thread overview]
Message-ID: <570B761D.7080304@redhat.com> (raw)
In-Reply-To: <mvm60vowjqa.fsf@hawking.suse.de>
On 04/11/2016 11:57 AM, Andreas Schwab wrote:
> Florian Weimer <fweimer@redhat.com> writes:
>
>> I removed it, built a special libdofork.so which has a DT_NEEDED entry for
>> libpthread.so.0 only,
>
> Did you build libdofork before removing the wrapper?
Yes, I did, and I linked explicitly with -lpthread. After that, I
patched out the DT_NEEDED entry:
Dynamic segment contains 31 entries:
Addr: 0x0000000000200db8 Offset: 0x000db8 Link to section: [ 4]
'.dynstr'
Type Value
NEEDED Shared library: [libpthread.so.0]
<unknown>: 0xff 0x000000000000008c
However, the symbol version is stilled mapped to libc.so.6:
Version symbols section [ 5] '.gnu.version' contains 14 entries:
Addr: 0x000000000000043a Offset: 0x00043a Link to section: [ 3]
'.dynsym'
0: 0 *local* 0 *local*
2: 0 *local* 0 *local*
4: 0 *local* 0 *local*
6: 2 GLIBC_2.2.5(libc.so.6) 2 GLIBC_2.2.5(libc.so.6)
8: 1 *global* 1 *global*
10: 1 *global* 1 *global*
12: 1 *global* 1 *global*
Version needs section [ 6] '.gnu.version_r' contains 1 entry:
Addr: 0x0000000000000458 Offset: 0x000458 Link to section: [ 4]
'.dynstr'
000000: Version: 1 File: libc.so.6 Cnt: 1
0x0010: Name: GLIBC_2.2.5 Flags: none Version: 2
I don't know how t get rid of that.
Florian
prev parent reply other threads:[~2016-04-11 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 13:19 Florian Weimer
2016-03-30 13:38 ` Andreas Schwab
2016-03-30 16:47 ` Richard Henderson
2016-03-30 19:10 ` Szabolcs Nagy
2016-03-30 19:51 ` Richard Henderson
2016-04-11 9:34 ` Florian Weimer
2016-04-11 9:58 ` Andreas Schwab
2016-04-11 10:02 ` Florian Weimer [this message]
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=570B761D.7080304@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nsz@port70.net \
--cc=roland@hack.frob.com \
--cc=rth@redhat.com \
--cc=schwab@suse.de \
/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).