Messages in this thread | | | Date | Sun, 26 Mar 2006 09:27:44 -0700 | From | Andreas Dilger <> | Subject | Re: [Ext2-devel] [PATCH 1/2] ext2/3: Support 2^32-1 blocks(Kernel) |
| |
On Mar 25, 2006 11:51 -0300, cascardo@minaslivre.org wrote: > As AMS has pointed out, the filesystem creator must be set to Hurd for > these inode fields to be used. Since ext2 seems to be the most > supported filesystem on Hurd, most of the ext2 fs used have the fs > creator set to Hurd.
So, if fs creator is Linux then HURD doesn't try to use those fields? That would allow Linux to start using them, and if such a filesystem is used on HURD then it could store the translator/author/mode_high in the xattr space. Does it even make sense to add translator/author to existing files, or only at file creation time?
That would mean that Linux would just need to check the fs creator field before using any of the HURD-reserved fields.
> Regarding compatibility, there are plans to support xattr in Hurd and > use them for these fields, translator and author. (I can't recall what > i_mode_high is used for.) With respect to that, I'd appreciate if > there is a recommendation to every ext2 implementation (not only > Linux) that supports xattr, to support gnu.translator and gnu.author > (I'll check about the i_mode_high and post about it asap.).
Not that we will be in a rush to use these fields, but it would be good to know what i_mode_high is used for in case it ever becomes relevant for Linux we would want to keep it the same meaning as HURD.
> There is a > patch by Roland McGrath for Linux that supports those besides the > reserved fields in case the fs creator is Hurd.
I'm not sure what is required for supporting such EAs? I don't think any kernel would remove existing EAs, even if it doesn't understand them.
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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |