diff options
author | Szabolcs Nagy <nsz@port70.net> | 2019-05-16 17:15:33 +0000 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2019-05-16 20:12:56 -0400 |
commit | 6104dae9088da7ffd9346671be867a43a4b03295 (patch) | |
tree | 410a27383126be084e4b92a6ec3d9621d8663d99 /VERSION | |
parent | 9fd98a6354105dd67b648b48dba238f4c3e3d564 (diff) | |
download | musl-6104dae9088da7ffd9346671be867a43a4b03295.tar.gz musl-6104dae9088da7ffd9346671be867a43a4b03295.tar.bz2 musl-6104dae9088da7ffd9346671be867a43a4b03295.tar.xz musl-6104dae9088da7ffd9346671be867a43a4b03295.zip |
fix static tls offsets of shared libs on TLS_ABOVE_TP targets
tls_offset should always point to the end of the allocated static tls
area, but this was not handled correctly on "tls variant 1" targets
in the dynamic linker:
after application tls was allocated, tls_offset was aligned up,
potentially wasting tls space. (alignment may be needed at the
begining of the tls area, not at the end, but that will be fixed
separately as it is unlikely to affect real binaries.)
when static tls was allocated for a shared library, tls_offset was
only updated with the size of the tls segment which does not include
alignment gaps, which can easily happen if the tls size update for
one library leaves tls_offset misaligned for the next one. this can
cause oob access in __copy_tls or arbitrary breakage at tls access.
(the issue was observed on aarch64 with rust binaries)
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions