On Wed, Aug 17, 2016 at 2:37 PM, Rik van Riel <[email protected]> wrote:
>
> This particular allocation is through kmalloc, but the
> kernel in question has CONFIG_SLOB=y, and usercopy has
> no code in mm/slob.c
Oh, I didn't notice that.
Maybe we can just say that HARDENING depends on !SLOB for now, and see
if anything else shows up.
Maybe we don't have any code that copies data from (non-kmalloc)
multi-order allocations to user space.
Networking does, but seems to use __GFP_COMP, at least in the one case
I checked (skbuff).
Linus
