| 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: <20081022204053.GA10369@mit.edu> Date: Wed, 22 Oct 2008 16:40:53 -0400 From: Theodore Tso <tytso@....edu> To: Phillip Susi <psusi@....rr.com> Cc: Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Yea old defrag On Wed, Oct 22, 2008 at 04:01:48PM -0400, Phillip Susi wrote: > > I have been trying to identify any new features that cause problems and > fix any that arise. Aren't extended attributes stored in the extra > space of large inodes? If so, I would need to format a new fs using > large inodes to test. Extended attributes *can* be stored in the extra space of large inodes, but they can also be stored in separate, stand-alone data blocks --- and just to make life entertaining, if multiple files have exactly the same set of extended attributes (for example, if all of the files inone directory have the same ACL and/or SELinux property), an extended attribute block can be shared across multiple inodes for space efficiency. > Are there any other ext3 features that might cause trouble? I know > there are plenty in ext4, but I want to make sure everything works well > in ext3 first. That's probably the main one; and as you say, there are plenty of new features that will require special handling for e2defrag, especially since it doesn't use the standard libext2fs library. - Ted -- 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