Re: [kernel-hardening] Project convention on configuration options

[Daniel Micay <danielmicay@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

> I think there will be plenty of bike-shedding, so pick whatever you
> like for now. :)
> 
> There is already the (disabled due to gcc bugs)
> DEBUG_STRICT_USER_COPY_CHECKS (which should lose the "DEBUG" name
> too). IIRC, it works by tracking memory regions? Maybe TRACK_USERCOPY?
> I'm sure it'll get renamed, so no big deal. In fact, you could just
> leave it as PAX_USERCOPY too for the initial extraction.

The main component is dynamically querying the slab allocator for the
allocation sizes. It also has checking for stack frames and global data.
There are also some tweaks related to __builtin_object_size.

It would make sense to land it in pieces, perhaps starting with the slab
allocator stuff (which is the bulk of the changes since some slabs need
to be marked and it seems like it would be the least controversial part
of the feature).

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]