| 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
| ||
|
Message-id: <20081125211043.GT3186@webber.adilger.int> Date: Tue, 25 Nov 2008 14:10:43 -0700 From: Andreas Dilger <adilger@....com> To: Solofo.Ramangalahy@...l.net Cc: Theodore Tso <tytso@....EDU>, linux-ext4@...r.kernel.org Subject: Re: [RFC 0/2] ext4: zero uninitialized inode tables On Nov 25, 2008 13:28 +0100, Solofo.Ramangalahy@...l.net wrote: > Appart from the data structures change you mentionned, these changes > were discussed: > . a mount option to disable the threads when doing testing/performance > benchmarking Sure. > . a flag in s_flags field of struct ext4_super_block to indicate that > the zeroing has been done on all the groups. Possibly reset with > resize. I was thinking that it makes sense to have this same thread do checking of all the block group metadata as it traverses the filesystem. That includes validating the GDT checksums, checking the existing block and inode bitmaps (and possibly checksums for them, when that is implemented), along with zeroing the inode table. The only requirement is that there only be a single such thread running on the filesystem at one time, and that if the filesystem is unmounted that the thread be killed before the unmount is completed. 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