| 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
| ||
|
Date: Thu, 08 May 2008 16:48:47 -0600 From: Andreas Dilger <adilger@....com> To: "Theodore Ts'o" <tytso@....edu> Cc: linux-ext4@...r.kernel.org Subject: mke2fs and lazy_itable_init I just noticed lazy_itable_init in the mke2fs.8.in man page. I think a warning needs to be added there that this is not currently safe to use, because the kernel does not yet do the background zeroing. There is nothing in the man page to indicate that this is unsafe... .B lazy_itable_init\fR[\fb= \fI<0 to disable, 1 to enable>\fR] If enabled and the uninit_bg feature is enabled, the inode table will not fully initialized by .BR mke2fs . This speeds up filesystem initialization noitceably, but it requires the kernel to finish initializing the filesystem in the background when the filesystem is first mounted. If the option value is omitted, it defaults to 1 to enable lazy inode table initialization. +.BR NOTE : +No kernels do the background zeroing of the inode table at this time, +so this option is unsafe for production use, due to the risk of serious +filesystem corruption if e2fsck has to scan the whole inode table for +some reason (e.g. incorrect group descriptor checksum). Sorry for half patch, but my GIT repo is broken somehow and I wanted to email before I forget. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- 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
Powered by blists - more mailing lists