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: Florian Weimer <fweimer at redhat dot com>
- To: Sergey Senozhatsky <sergey dot senozhatsky dot work at gmail dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, Carlos O'Donell <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, Sergey Senozhatsky <sergey dot senozhatsky at gmail dot com>
- Date: Mon, 13 Aug 2018 13:10:37 +0200
- 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>
On 08/13/2018 06:51 AM, Sergey Senozhatsky wrote:
[ 8.864561] process: tty: Unsupported common prctl 3001
[ 8.865664] expr: Unsupported prctl 3001
Which is, maybe fine, though I'm not entirely sure since I don't
really see ARCH_CET being supported by any arch (neither in linux-next
nor in Linus' tree), so maybe as of now those syscalls are unneeded.
Which kernel version is that? The above looks like a kernel bug because
there doesn't seem to be any rate limiting.
The part where, I believe, these -EINVAL prctls begin to backfire is
valgrind - I can't run it anymore with glibc 2.28. It gives me the
valgrind has already been fixed: