linux-kernel - Re: next-20080808: bash: fork: Resource temporarily unavailable

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]

Message-ID: <15386.1218290826@redhat.com>
Date:	Sat, 09 Aug 2008 15:07:06 +0100
From:	David Howells <dhowells@...hat.com>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	dhowells@...hat.com, James Morris <jmorris@...ei.org>,
	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Linux-Next <linux-next@...r.kernel.org>
Subject: Re: next-20080808: bash: fork: Resource temporarily unavailable

Thomas Meyer <thomas@...3r.de> wrote:

> Is that what you wanted to know? Doesn't look like a memory leak for me.

It wasn't really what I was after, but I agree, with only 24.4 MB allocated to
slabs, it doesn't look like a leak.

> kmem: invalid structure member offset: kmem_cache_objects
>       FILE: memory.c  LINE: 13500  FUNCTION: dump_kmem_cache_slub()

That smacks of the internal structs having changed more recently than F9's
kmem program.

I guess I need to get this thing running on an i386 box.

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/