linux-ext4 - Re: Memory allocation failed, e2fsck: aborted

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:	Thu, 19 Aug 2010 13:16:20 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Andre Noll <maan@...temlinux.org>
Cc:	Andreas Dilger <adilger@...ger.ca>,
	linux-ext4 <linux-ext4@...r.kernel.org>,
	Marcus Hartmann <marcus.hartmann@...bingen.mpg.de>
Subject: Re: Memory allocation failed, e2fsck: aborted

On Thu, Aug 19, 2010 at 03:10:17PM +0200, Andre Noll wrote:
> Silly question: Would it be possible to simply mmap a large enough
> file for the data and and use e.g. rbtrees for the lookups? If yes,
> osl [1] could probably be an option. It's very simple but likely too
> slow on inserts to be useful for e2fsprogs.

As I recall, you're on a 32-bit machine, right?  If so, a limitation
you may run into is simply running out of address space.  If it's not
an address space issue, we don't need to mmap anything; you could just
try enabling swap, and use the existing e2fsck code.

(I had assumed you had tried that before suggesting you use the
scratch_files tdb approach....)

					- 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