diff options
author | Matthew Malcomson <matthew.malcomson@arm.com> | 2022-03-17 15:40:52 +0000 |
---|---|---|
committer | Matthew Malcomson <matthew.malcomson@arm.com> | 2022-03-17 15:41:08 +0000 |
commit | dd0ed54c1a4e459f6f1a8331499eb63520d31a75 (patch) | |
tree | fb6ee8f5a7ceff172f2c4c310da6a8ccbc07fa6b /config.sub | |
parent | 49432a1df068164f265ab9c6bf4d86f5e984762c (diff) | |
download | gdb-dd0ed54c1a4e459f6f1a8331499eb63520d31a75.zip gdb-dd0ed54c1a4e459f6f1a8331499eb63520d31a75.tar.gz gdb-dd0ed54c1a4e459f6f1a8331499eb63520d31a75.tar.bz2 |
Add a size to __ehdr_start
This symbol is defined in a binary when there is a segment which
contains both the file header and the program header. The symbol points
at the file header. The point of this symbol is to allow the program to
robustly examine its own output.
Glibc uses this symbol. This symbol is currently not marked as a
linker or linker script defined symbol, and hence does not get its
bounds adjusted. The symbol is given zero size, and consequently any
capability initialised as a relocation to this symbol is given zero
bounds.
In order to allow access to read the headers this symbol points at this
patch adds a size to the symbol.
We do not believe that the size of this symbol is used for anything
other than CHERI bounds, so we believe that this is a safe change to
make. Setting the size of the symbol means that c64_fixup_frag uses
that size as the bounds to apply to a capability relocation pointing at
that symbol. This allows access to the file and program headers loaded
into memory.
An alternative approach would be to *not* set the size of the symbol,
but only change the bounds of the relocation generated. This would be
done by checking for the `__ehdr_start' name in c64_fixup_frag and
setting the size according to the `sizeof_ehdr' and
`elf_program_header_size' values stored on the output BFD object.
We chose the approach to set the size on the symbol for code-aesthetic
reasons under the belief that having this size on the symbol in the
final binary is a slight benefit in readability for a user and causes no
downside.
I do not believe that Morello lld sets the bounds of a capability to this
symbol correctly. That issue has been raised separately.
Diffstat (limited to 'config.sub')
0 files changed, 0 insertions, 0 deletions