linux-kernel - Re: kmemleak, cpu usage jump out of nowhere

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100715191638.GA3694@brouette>
Date:	Thu, 15 Jul 2010 21:16:38 +0200
From:	Damien Wyart <damien.wyart@...e.fr>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Zeno Davatz <zdavatz@...il.com>,
	Catalin Marinas <catalin.marinas@....com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
	mingo@...e.hu, yinghai@...nel.org
Subject: Re: kmemleak, cpu usage jump out of nowhere

> > > I also did not have anymore hangs and random bad moods of my CPUs
> > > that all of a sudden grab 100% of all 8 cores of my CPU power across
> > > my machine since I disabled
> > > CONFIG_NO_BOOTMEM:

> * Pekka Enberg <penberg@...helsinki.fi> [2010-07-15 18:54]:
> > Interesting. Damien, does disabling CONFIG_NO_BOOTMEM fix you problem too?

> I will test in the coming hours, and report back tomorrow... Just
> recompiled 2.6.35-rc5-git1 with this option disabled.

For now, I can't reproduce the problem with CONFIG_NO_BOOTMEM disabled ;
with the option and rc5 the problem was happening quite quickly after
boot and normal use of the machine. So it seems I can confirme what Zeno
has seen and I hope this will give a hint to debug the problem. I guess
this has not been reported that much because many testers might not have
enabled CONFIG_NO_BOOTMEM... Maybe the scheduler folks could test their
benchmark with a kernel having this option enabled?

-- 
Damien
--
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/