From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] Fix TLS layout of TLS variant I when there is a gap above TP
Date: Sat, 2 Jun 2018 21:11:21 -0400 [thread overview]
Message-ID: <20180603011121.GU1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180602071523.GP4418@port70.net>
On Sat, Jun 02, 2018 at 09:15:23AM +0200, Szabolcs Nagy wrote:
> * Rich Felker <dalias@libc.org> [2018-06-01 22:59:11 -0400]:
> > On Sat, Jun 02, 2018 at 01:52:01AM +0200, Szabolcs Nagy wrote:
> > > In TLS variant I the TLS is above TP (or above a fixed offset from TP)
> > > but on some targets there is a reserved gap above TP before TLS starts.
> > >
> > > This matters for the local-exec tls access model when the offsets of
> > > TLS variables from the TP are hard coded by the linker into the
> > > executable, so the libc must compute these offsets the same way as the
> > > linker. The tls offset of the main module has to be
> > >
> > > alignup(GAP_ABOVE_TP, main_tls_align).
> > >
> > > If there is no TLS in the main module then the gap can be ignored
> > > since musl does not use it and the tls access models of shared
> > > libraries are not affected.
> > >
> > > The previous setup only worked if (tls_align & -GAP_ABOVE_TP) == 0
> > > (i.e. TLS did not require large alignment) because the gap was
> > > treated as a fixed offset from TP. Now the TP points at the end
> > > of the pthread struct (which is aligned) and there is a gap above
> > > it (which may also need alignment).
> > >
> > > The fix required changing TP_ADJ and __pthread_self on affected
> > > targets (aarch64, arm and sh) and in the tlsdesc asm the offset to
> > > access the dtv changed too.
> > > ---
> >
> > On first glance it all looks right. I'll read in more detail soon.
> > Thanks!
> >
> > > passed my simple local-exec tests.
> >
> > Did you test all archs or just some? I think we should at least run
> > libc-test (if it sufficiently tests TLS) on the affected archs to make
> > sure there are no regressions.
> >
>
> ran libc-test on various targets via qemu-user, i didnt see any regressions.
I just setup libc-test to run under qemu-system-sh4, and confirmed
failure before the patch, success with the patch applied. I don't have
any other qemu-system environments setup, but success here looks like
a good sign!
Rich
next prev parent reply other threads:[~2018-06-03 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 23:52 Szabolcs Nagy
2018-06-02 2:59 ` Rich Felker
2018-06-02 7:15 ` Szabolcs Nagy
2018-06-03 1:11 ` Rich Felker [this message]
2018-06-04 7:27 ` Phillip Berndt
2018-06-11 19:02 ` Phillip Berndt
2018-06-11 19:14 ` Rich Felker
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=20180603011121.GU1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).