Hello,
I've got the same issue on PPC32 with hugepages:
unreferenced object 0xc30f8200 (size 512):
comm "mmap", pid 374, jiffies 4872494 (age 627.630s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00
Paul Menzel writes:
> On 07/30/18 08:43, Michael Ellerman wrote:
>> Paul Menzel writes:
>>> Am 19.07.2018 um 16:33 schrieb Michael Ellerman:
>> ...
The fix is fairly simple. We need to tell kmemleak to ignore PUD
allocations and never report them as leaks. We can also tell it not t
Dear Michael,
On 07/30/18 08:43, Michael Ellerman wrote:
> Paul Menzel writes:
>> Am 19.07.2018 um 16:33 schrieb Michael Ellerman:
> ...
>>>
>>> The fix is fairly simple. We need to tell kmemleak to ignore PUD
>>> allocations and never report them as leaks. We can also tell it not to
>>> scan th
Paul Menzel writes:
> Am 19.07.2018 um 16:33 schrieb Michael Ellerman:
...
>>
>> The fix is fairly simple. We need to tell kmemleak to ignore PUD
>> allocations and never report them as leaks. We can also tell it not to
>> scan the PGD, because it will never find pointers in there. However it
>>
Dear Michael,
Am 19.07.2018 um 16:33 schrieb Michael Ellerman:
Paul Menzel reported that kmemleak was producing reports such as:
unreferenced object 0xc000f8b8 (size 16384):
comm "init", pid 1, jiffies 4294937416 (age 312.240s)
hex dump (first 32 bytes):
00 00 00 00
Paul Menzel reported that kmemleak was producing reports such as:
unreferenced object 0xc000f8b8 (size 16384):
comm "init", pid 1, jiffies 4294937416 (age 312.240s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 0
