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  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:	Mon, 27 Sep 2010 14:35:52 -0400
From:	Ted Ts'o <>
To:	Lukas Czerner <>
Subject: Re: [PATCH 2/6] Add inititable/noinititable mount options for ext4

On Thu, Sep 16, 2010 at 02:47:27PM +0200, Lukas Czerner wrote:
> Add new mount flag EXT4_MOUNT_INIT_INODE_TABLE and add new pair of mount
> options (inititable/noinititable). When mounted with inititable file
> system should try to initialize uninitialized inode tables, otherwise it
> should prevent initializing inode tables. For now, default is noinittable.
> One can also specify inititable=n where n is a number that will be used
> as the wait multiplier (see "Add inode table initialization code into
> Ext4" patch for more info). Bigger number means slower inode table
> initialization thus less impact on performance, but longer
> inititalization (default is 10).

Note: this patch doesn't compile on its own, since it uses s_li_wait
before it is defined (in the next patch).

This is a problem if someone tries to do a "git bisect" and lands
between these two patches.

I'll probably fix this just by merging these two patches together...

     	      	       	       	       - Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists