On 10/02/2014 07:58 AM, Sasha Levin wrote:
>> > What does this add on top of slab poisoning? Some checks in some
>> > mm places while the object is active, I guess: why not base those
>> > on slab poisoning? And add them in as appropriate to the problem
>> > at hand, when a problem is seen.
> The extra you're getting is detecting corruption that happened
> inside the object rather than around it.
Isn't this more akin to redzoning that poisoning?
I'm not sure I follow the logic here. The poison is inside the object,
but it's now at the edges. With slub at least, you get a redzone right
after the object(s):
{ OBJ } | REDZONE | { OBJ } | REDZONE | ...
With this patch, you'd get something along these lines:
{ POISON | OBJ | POISON } { POISON | OBJ | POISON } ...
So if somebody overflows OBJ, they'll hit the redzone/poison in either
case. If they're randomly scribbling on memory, their likelihood of
hitting the redzone/poison is proportional to the size of the
redzone/poison.
The only place this really helps is if someone overflows from a
non-redzoned page or structure in to the beginning of a slub redzoned
one. The fact that the redzone is at the end means we'll miss it.
But, all that means is that we should probably add redzones to the
beginning of slub objects, not just the end. That doesn't help us with
'struct page' of course, but it does for the mm_struct and vma.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>