>> +++ b/mm/kmemleak.c
>> @@ -555,7 +555,6 @@ static struct kmemleak_object *create_object(unsigned long ptr, size_t size,
>>
>> object = kmem_cache_alloc(object_cache, gfp_kmemleak_mask(gfp));
>> if (!object) {
>> - pr_warn("Cannot allocate a kmemleak_object structure\n");
>> kmemleak_disable();
>
> I don't really get what this patch is trying to achieve.
I suggest to reduce the code size a bit.
> Given that kmemleak will be disabled after this,
I have got difficulties to interpret this information.
> I'd rather know why it happened.
Do you find the default allocation failure report sufficient?
Regards,
Markus
--
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>
