linux-ext4 - Re: ext4_alloc_context occupies 150 GiB of memory and makes the system unusable

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: <20101205031130.GA4273@thunk.org>
Date:	Sat, 4 Dec 2010 22:11:30 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Christoph Bartoschek <bartoschek@...uni-bonn.de>,
	linux-ext4@...r.kernel.org
Subject: Re: ext4_alloc_context occupies 150 GiB of memory and makes the
 system unusable

Christoph,

Have you been able to replicate this problem since rebooting your
machine.  I've never seen anything quite like your report before.

If you do, a couple of questions.  Which slab allocator are you using?
Are you using SLAB or SLUB?  (grep for CONFIG_SLAB or CONFIG_SLUB in
your .config file).

If you are using SLUB, it would be useful to compile slubinfo.c (found
in /usr/src/linux/Documentation/vm/slabinfo.c) and send us the output
"slabinfo -a ext4_allocation_context" and "slabinfo -r
ext4_allocation_context".   

Also, you might try "slabinfo -s" and see if that shrinks the slabs
for you.  If this works, why it wasn't doing this automatically is
beyond me.

					- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html