On 04.01.2018 21:49, m...@netbsd.org wrote: > Also, I understand that to exploit this, one has to attempt to access > kernel memory a lot, and SEGV at least once per bit. > > I wonder if we can count the number of SEGVs and if we get a few, turn > on the workaround? that would at least spare us the performance penalty > for normal code. >
We have: PaX Segvguard. Can we mitigate it with this feature?
signature.asc
Description: OpenPGP digital signature
