Strict memcpy() bounds checking for the kernel
Strict memcpy() bounds checking for the kernel
Posted Jul 30, 2021 21:33 UTC (Fri) by mathstuf (subscriber, #69389)In reply to: Strict memcpy() bounds checking for the kernel by post-factum
Parent article: Strict memcpy() bounds checking for the kernel
Isn't that just for static structures full of function pointers (basically vtables)? Presumably `sk_buff` structures and other such things being `memcpy`'d to are not constant once the kernel is booted.
Posted Aug 2, 2021 15:07 UTC (Mon)
by kees (subscriber, #27264)
[Link]
Strict memcpy() bounds checking for the kernel
Right, and if any __randomize_layout struct wanted to use struct_group() it could as those would be kept together. It actually makes things easier.