linux-ext4 - Re: [PATCH] allow goal inode to be specified

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: <20090613154811.GL24336@mit.edu>
Date:	Sat, 13 Jun 2009 11:48:11 -0400
From:	Theodore Tso <tytso@....edu>
To:	Andreas Dilger <adilger@....com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] allow goal inode to be specified

On Wed, Jun 10, 2009 at 02:27:02PM -0600, Andreas Dilger wrote:
> Allow a goal inode to be specified when allocating new inodes.
> If the goal is within the range of valid inodes use this in
> preference to one of the other target inode heuristics (Orlov or
> parent directory).
> 
> The goal inode can be specified via /sys/fs/{dev}/inode_goal for
> testing inode allocation beyond 2^32 blocks on very large filesystems,
> and in the future will be used for large xattr inode allocation.

This patch didn't quite apply against the mainline ext4, and in
addition it conflicted with a patch to keep the choice of Orlov topdir
inode numbers stable for the purposes of benchmarking.  So instead I
dropped the following two patches into the ext4 patch queue.

	    	      	  	       	   	- 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