lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 14 Jul 2010 12:00:02 +0200
From:	Zeno Davatz <zdavatz@...il.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: kmemleak, cpu usage jump out of nowhere

On Wed, Jul 14, 2010 at 11:55 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> Catalin Marinas wrote:
>>
>> On Wed, 2010-07-14 at 09:27 +0100, Zeno Davatz wrote:
>>>
>>> On Wed, Jul 14, 2010 at 10:05 AM, Pekka Enberg <penberg@...helsinki.fi>
>>> wrote:
>>>>
>>>> On Wed, Jul 14, 2010 at 9:12 AM, Zeno Davatz <zdavatz@...il.com> wrote:
>>
>>>>> I am attaching you the file from /sys/kernel/debug/kmemleak
>>>>
>>>> Zeno, can you post your dmesg and .config, please?
>>>
>>> Sure, see attached files.
>>
>> It looks like NO_BOOTMEM is enabled. You can try the attached patch (I
>> need to post it again on the list).
>>
>>
>> kmemleak: Add support for NO_BOOTMEM configurations
>>
>> From: Catalin Marinas <catalin.marinas@....com>
>>
>> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
>> friends use the early_res functions for memory management when
>> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
>> corresponding code paths for bootmem allocations.
>>
>> Signed-off-by: Catalin Marinas <catalin.marinas@....com>
>> Cc: Yinghai Lu <yinghai@...nel.org>
>> Cc: H. Peter Anvin <hpa@...or.com>
>
> Makes sense.
>
> Acked-by: Pekka Enberg <penberg@...helsinki.fi>
>
> Zeno, this should fix the kmemleak false positives but not the big pauses
> you're seeing.

Thank for this detailed info Pekka! I will not apply the patch at the
moment. Will it be in with the next RC from Linus? Or do you recommend
I apply it?

What I want it is to tame the temper of Tux and restrict him from
eating my CPU-donuts (cores) at random. I need them for other
processes. ;)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ