From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: carlos <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha <libc-alpha@sourceware.org>,
Thomas Gleixner <tglx@linutronix.de>, Ben Maurer <bmaurer@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
Rich Felker <dalias@libc.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10)
Date: Fri, 14 Jun 2019 09:01:41 -0400 (EDT) [thread overview]
Message-ID: <1085273942.3137.1560517301721.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1190407525.3131.1560516910936.JavaMail.zimbra@efficios.com>
----- On Jun 14, 2019, at 2:55 PM, Mathieu Desnoyers mathieu.desnoyers@efficios.com wrote:
> ----- On Jun 14, 2019, at 1:35 PM, Florian Weimer fweimer@redhat.com wrote:
>
>> * Mathieu Desnoyers:
>>
>>> * Makefile:
>>>
>>> LIBCPATH=/home/efficios/glibc-test/lib
>>> KERNEL_HEADERS=/home/efficios/git/linux-percpu-dev/usr/include
>>> CFLAGS=-I${KERNEL_HEADERS} -L${LIBCPATH} -Wl,--rpath=${LIBCPATH}
>>> -Wl,--dynamic-linker=${LIBCPATH}/ld-linux-x86-64.so.2
>>>
>>> all:
>>> gcc ${CFLAGS} -o a a.c
>>> gcc ${CFLAGS} -shared -fPIC -o s.so s.c
>>
>> For me, that does not correctly link against the built libc because the
>> system dynamic loader seeps into the link.
>
> I have the same issue. I tried adding "-B${LIBCPATH}" as well, but it did
> not seem to help. I still have this ldd output:
>
> ldd a
> ./a: /lib64/ld-linux-x86-64.so.2: version `GLIBC_2.30' not found (required by
> ./a)
> linux-vdso.so.1 (0x00007fffaa7e9000)
> libc.so.6 => /home/efficios/glibc-test/lib/libc.so.6 (0x00007fac5d479000)
> /home/efficios/glibc-test/lib/ld-linux-x86-64.so.2 =>
> /lib64/ld-linux-x86-64.so.2 (0x00007fac5da33000)
>
> Still no luck there. Any idea what compiler/linker flag I am missing ?
>
Actually, even though ldd seems confused, running the program seems to
use the right ld.so:
efficios@compudjdev:~/test/libc-sym$ ./a
__rseq_handled main: 1 0x55f0ec915020
__rseq_abi.cpu_id main: 28 0x7f54f6c2d4c0
efficios@compudjdev:~/test/libc-sym$ LD_PRELOAD=./s.so ./a
__rseq_handled s.so: 1 0x557350bc6020
__rseq_abi.cpu_id s.so: -1 0x7fe2f30f2680
__rseq_handled main: 1 0x557350bc6020
__rseq_abi.cpu_id main: 27 0x7fe2f30f2680
But my original issue remains: if I define a variable called __rseq_handled
within either the main executable or the preloaded library, it overshadows
the libc one:
efficios@compudjdev:~/test/libc-sym$ ./a
__rseq_handled main: 0 0x56135fd5102c
__rseq_abi.cpu_id main: 29 0x7fcbeca6d5a0
efficios@compudjdev:~/test/libc-sym$ LD_PRELOAD=./s.so ./a
__rseq_handled s.so: 0 0x558f70aeb02c
__rseq_abi.cpu_id s.so: -1 0x7fdca78b7760
__rseq_handled main: 0 0x558f70aeb02c
__rseq_abi.cpu_id main: 27 0x7fdca78b7760
Which is unexpected.
This is with my dev branch at this commit:
https://github.com/compudj/glibc-dev/commit/f0d4e60e5d0ceb0c2642f99da5af61b6ad988531
What am I missing ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2019-06-14 13:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190503184219.19266-1-mathieu.desnoyers@efficios.com>
2019-05-03 18:42 ` [PATCH 1/5] glibc: Perform rseq(2) registration at C startup and thread creation (v10) Mathieu Desnoyers
2019-05-27 11:19 ` Florian Weimer
2019-05-27 19:27 ` Mathieu Desnoyers
2019-05-29 15:45 ` Mathieu Desnoyers
2019-05-30 20:56 ` Mathieu Desnoyers
2019-05-31 8:06 ` Florian Weimer
2019-05-31 14:48 ` Mathieu Desnoyers
2019-05-31 15:46 ` Florian Weimer
2019-05-31 18:10 ` Mathieu Desnoyers
2019-06-04 11:46 ` Florian Weimer
2019-06-04 15:57 ` Mathieu Desnoyers
2019-06-06 11:57 ` Florian Weimer
2019-06-10 14:43 ` Carlos O'Donell
2019-06-12 14:00 ` Mathieu Desnoyers
2019-06-14 10:03 ` Mathieu Desnoyers
2019-06-14 10:06 ` Florian Weimer
2019-06-14 10:14 ` Mathieu Desnoyers
2019-06-14 11:35 ` Florian Weimer
2019-06-14 12:55 ` Mathieu Desnoyers
2019-06-14 13:01 ` Mathieu Desnoyers [this message]
2019-06-14 13:09 ` Florian Weimer
2019-06-14 13:18 ` Mathieu Desnoyers
2019-06-14 13:24 ` Florian Weimer
2019-06-14 13:34 ` Mathieu Desnoyers
2019-06-14 13:42 ` Florian Weimer
2019-06-14 13:47 ` Mathieu Desnoyers
2019-06-14 13:53 ` Florian Weimer
2019-06-14 13:59 ` Mathieu Desnoyers
2019-06-14 13:29 ` David Laight
2019-06-14 13:39 ` Mathieu Desnoyers
2019-06-12 14:16 ` Mathieu Desnoyers
2019-06-12 14:22 ` Florian Weimer
2019-06-12 14:36 ` Mathieu Desnoyers
2019-06-12 14:43 ` Florian Weimer
2019-05-03 18:42 ` [PATCH 2/5] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux (v4) Mathieu Desnoyers
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=1085273942.3137.1560517301721.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=davejwatson@fb.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=szabolcs.nagy@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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