about summary refs log tree commit diff
path: root/sysdeps/unix/sysv/linux/semtimedop.c
diff options
context:
space:
mode:
authorCarlos O'Donell <carlos@redhat.com>2018-11-20 17:06:30 -0500
committerCarlos O'Donell <carlos@redhat.com>2018-11-26 21:23:50 -0500
commitce035c6e909ad20ef2fe13c92eab4e69f6495b61 (patch)
tree961f6223de461e85f9f3c4204a539bdb54da9292 /sysdeps/unix/sysv/linux/semtimedop.c
parent2bd0bfcc6857f1fde2bd9716dc103333ebaa6807 (diff)
downloadglibc-ce035c6e909ad20ef2fe13c92eab4e69f6495b61.tar.gz
glibc-ce035c6e909ad20ef2fe13c92eab4e69f6495b61.tar.xz
glibc-ce035c6e909ad20ef2fe13c92eab4e69f6495b61.zip
abilist.awk: Treat .tdata like .tbss and reject unknown combinations.
Mathieu Desnoyers ran into an issue with his rseq patch where he
was the first person to add weak thread-local data and this
resulted in an ABI list update with entries like this:
"GLIBC_2.29 w ? D .tdata 0000000000000020".

The weakness of the symbol has nothing to do with the DSOs ABI
and so we should not write anything about weak symbols here. The
.tdata entries should be treated exactly like .tbss entries and
the output should have been: "GLIBC_2.29 __rseq_abi T 0x20"

This change makes abilist.awk handle .tdata just like .tbss,
while at the same time adding an error case for the default, and
the unknown line cases.  We never want anyone to be able to add
such entries to any ABI list files and should see an immediate
error and consult with experts.

Tested by Mathieu Desnoyers <mathieu.desnoyers@efficios.com> with
the rseq patch set and 'make update-all-abi'.

Tested myself with 'make update-all-abi' on x86_64 with no
changes.

Signed-off-by: Carlos O'Donell <carlos@redhat.com>
Diffstat (limited to 'sysdeps/unix/sysv/linux/semtimedop.c')
0 files changed, 0 insertions, 0 deletions