Re: memory leak in alloc_huge_page

From: Mike Kravetz
Date: Tue Dec 01 2015 - 19:54:46 EST


On 12/01/2015 11:45 AM, Dmitry Vyukov wrote:
> On Tue, Dec 1, 2015 at 7:52 PM, Mike Kravetz <mike.kravetz@xxxxxxxxxx> wrote:
>> On 12/01/2015 06:04 AM, Dmitry Vyukov wrote:

>>> There seems to be another leak if nrg is not NULL on this path, but
>>> it's not what happens in my case since the WARNING does not fire.
>>
>> If nrg is not NULL, then it was added to the resv map and 'should' be
>> free'ed when the map is free'ed. This is not optimal, but I do not
>> think it would lead to a leak. I'll take a close look at this code
>> with an emphasis on the leak you discovered.
>
>
> Hi Mike,
>
> Note that it's not just a leak report, it is an actual leak. You
> should be able to reproduce it.
>

OK, finally found the bug which is in region_del(). It does not correctly
handle a "placeholder" region descriptor that is left after an aborted
operation when the start of the region to be deleted is for the same page.

I will have a patch shortly, after some testing.

--
Mike Kravetz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/