linux-kernel - Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)

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:	Tue, 23 Oct 2007 12:57:15 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Pekka Enberg <penberg@...helsinki.fi>
cc:	Alexey Dobriyan <adobriyan@...il.com>,
	linux-kernel@...r.kernel.org, linux-mm@...r.kernel.org,
	mel@...net.ie
Subject: Re: SLUB 0:1 SLAB (OOM during massive parallel kernel builds)

On Tue, 23 Oct 2007, Pekka Enberg wrote:

> > > cc1 invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
> 
> Christoph Lameter wrote:
> > Regular Order 0 alloc .... but why is there no memory available , reclaimed?
> 
> I am too wondering where all that memory is going. Logging /proc/meminfo and
> slabinfo -S (see Documentation/vm/slabinfo.c) every few minutes or so probably
> might help answering that question

__GFP_HARDWALL and __GFP_MOVABLE is set. I guess we have no cpusets on the 
box? Wonder what the antifrag status is? Can we get /proc/pagetypeinfo?


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