linux-kernel - Re: 3.15-rc3: boot of a xen PV guest fails when using a guest kernel with CONFIG_DEBUG

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] [day] [month] [year] [list]

Message-ID: <1029422291.20140506195811@eikelenboom.it>
Date:	Tue, 6 May 2014 19:58:11 +0200
From:	Sander Eikelenboom <linux@...elenboom.it>
To:	David Vrabel <david.vrabel@...rix.com>
CC:	Pekka Enberg <penberg@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: 3.15-rc3: boot of a xen PV guest fails when using a guest kernel with CONFIG_DEBUG_SLAB=y


Tuesday, May 6, 2014, 11:51:04 AM, you wrote:

> On 02/05/14 22:01, Sander Eikelenboom wrote:
>> Hi,
>> 
>> On a machine running Xen-Unstable, i just tried running a 3.15-rc3 kernel with 
>> CONFIG_DEBUG_SLAB=y
>> 
>> [    0.748297] Kernel panic - not syncing: Out of memory and no killable processes...
>> [    0.748297]
>> [    0.748305] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc3-20140502-nbdebug12-slabdb+ #1
>> [    0.748310]  00000000002040d0 ffff88000ee9fa48 ffffffff81b8da66 ffff88000ee9c010
>> [    0.748317]  ffffffff81f5a8a0 ffff88000ee9fac8 ffffffff81b89bfb 0000000000000000
>> [    0.748325]  ffffffff00000008 ffff88000ee9fad8 ffff88000ee9fa78 ffffffff811952fa
>> [    0.748332] Call Trace:
>> [    0.748336]  [<ffffffff81b8da66>] dump_stack+0x46/0x58
>> [    0.748340]  [<ffffffff81b89bfb>] panic+0xd2/0x207
>> [    0.748345]  [<ffffffff811952fa>] ? out_of_memory+0x39a/0x5a0
>> [    0.748350]  [<ffffffff811954fe>] out_of_memory+0x59e/0x5a0


> Your guest is out of memory.  Give it some more?

The guest has 512MB assigned to it and it worked fine with:
- SLAB without DEBUG_SLAB
- SLUB with and without DEBUG_SLUB

It ooms with:
- SLAB with DEBUG_SLAB

With 1024MB assigned it seems to boot fine in all cases, so it seems DEBUG_SLAB 
is quite memory consuming when it fails in the first second of boot on 512MB.

--
Sander

> David



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