This is the mail archive of the
mailing list for the glibc project.
Re: rseq/arm32: choosing rseq code signature
- From: Florian Weimer <fweimer at redhat dot com>
- To: Mathieu Desnoyers <mathieu dot desnoyers at efficios dot com>
- Cc: Will Deacon <will dot deacon at arm dot com>, libc-alpha <libc-alpha at sourceware dot org>, linux-kernel <linux-kernel at vger dot kernel dot org>, Carlos O'Donell <carlos at redhat dot com>
- Date: Thu, 11 Apr 2019 14:24:10 +0200
- Subject: Re: rseq/arm32: choosing rseq code signature
- References: <1050734985.2625.1554838340011.JavaMail.email@example.com>
* Mathieu Desnoyers:
> * TODO: document trap instruction objdump output on each sub-architecture
> * instruction sets, as well as instruction set extensions.
> #define RSEQ_SIG 0x########
Will RSEQ_SIG actually be needed at run time outside the rseq
implementation library (whether it's glibc or something else)?
Actually rseq users will emit the signature directly into the text
section, right? They never have to load it into a register, I assume.
My concern is that on some architectures, the very act of referencing
RSEQ_SIG will put it into the text section, as a non-instruction, which
is not what we want.