This is the mail archive of the
mailing list for the glibc project.
Re: V4 [PATCH 04/12] x86/CET: Extend arch_prctl syscall for CET control
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Sergey Senozhatsky <sergey dot senozhatsky dot work at gmail dot com>
- Cc: Sergey Senozhatsky <sergey dot senozhatsky at gmail dot com>, Florian Weimer <fweimer at redhat dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, Joseph Myers <joseph at codesourcery dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 13 Aug 2018 23:02:02 -0400
- Subject: Re: V4 [PATCH 04/12] x86/CET: Extend arch_prctl syscall for CET control
- References: <CAMe9rOqKkgBp7PN9m-L7-r33brXO+Eu_=-7n74B=nS9FEujJhQ@mail.gmail.com> <20180813045118.GA1193@jagdpanzerIV> <email@example.com> <20180813123606.GA409@tigerII.localdomain> <firstname.lastname@example.org> <20180814004639.GA20631@jagdpanzerIV>
On 08/13/2018 08:46 PM, Sergey Senozhatsky wrote:
> These all are valid points, sure. But, somehow, testing for a feature
> that no kernel or HW supports looks *a bit* different. /etc/ld.so.preload
> at least exists on some hosts, while ARCH_CET does not. Maybe it's OK.
> My only real problem with ARCH_CET was valgrind.
Yes, the valgrind issue is a bummer, but we'll get that fixed in the downstream
distributions with a new valgrind version. If you are using bleeding edge glibc
you may also sometimes need the most recent developer tooling to understand
what it's doing :-}
I would also hope that all of our users are happy to have hardware enablement
early before hardware is available to consumers :-)