ext4: fix the mount option "init_itable=n" to work as expected for n=0
authorLukas Czerner <lczerner@redhat.com>
Fri, 20 May 2011 17:55:16 +0000 (13:55 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 20 May 2011 17:55:16 +0000 (13:55 -0400)
commit51ce65115642b77040f5582b8d2fc8815ac450f9
tree53e42bb73ccbca4251d46ec5705a40a6b61bc5ab
parente1290b3e62c496ade19939ce036f35bb69306820
ext4: fix the mount option "init_itable=n" to work as expected for n=0

For some reason, when we set the mount option "init_itable=0" it
behaves as we would set init_itable=20 which is not right at all.
Basically when we set it to zero we are saying to lazyinit thread not
to wait between zeroing the inode table (except of cond_resched()) so
this commit fixes that and removes the unnecessary condition.  The 'n'
should be also properly used on remount.

When the n is not set at all, it means that the default miltiplier
EXT4_DEF_LI_WAIT_MULT is set instead.

Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reported-by: Eric Sandeen <sandeen@redhat.com>
fs/ext4/super.c