linux-ext4 - Re: fuzz testing a KVM machine (x86) with ext4fs forces much more often the oom killer than btrfs

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: <20141125031512.GE31339@thunk.org>
Date:	Mon, 24 Nov 2014 22:15:12 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	Toralf Förster <toralf.foerster@....de>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: fuzz testing a KVM machine (x86) with ext4fs forces much more
 often the oom killer than btrfs

No idea; can you grab /proc/slabinfo and /proc/meminfo every minute or
so until it oom kills trinity?  Maybe that will give us a hint of at
least where the memory is getting consumed.

It could be the extent status tree cache, for which the need for a
better shrinker is a known bug that we're working on, but that's just
a wild guess.

Thanks,

						- 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