| 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: <20061026180133.GN3509@schatzie.adilger.int> Date: Thu, 26 Oct 2006 12:01:33 -0600 From: Andreas Dilger <adilger@...sterfs.com> To: Andre Noll <maan@...temlinux.org> Cc: Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org, Eric Sandeen <esandeen@...hat.com> Subject: Re: ext3: bogus i_mode errors with 2.6.18.1 On Oct 26, 2006 18:02 +0200, Andre Noll wrote: > On 03:36, Andreas Dilger wrote: > > The other issue is that you need to potentially set "num" bits in the > > bitmap here, if those all overlap metadata. In fact, it might just > > make more sense at this stage to walk all of the bits in the bitmaps, > > the inode table and the backup superblock and group descriptor to see > > if they need fixing also. > > I tried to implement this, but I could not find out how to check at this > point whether a given bit (in the block bitmap, say) needs fixing. Well, since we know at least one bit needs fixing and results in the block being written to disk then setting the bits for all of the other metadata blocks in this group has no extra IO cost (only a tiny amount of CPU). Re-setting the bits if they are already set is not harmful. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists