Re: Correct EXT3_TOPDIR_FL behaviour

[Andreas Dilger]

On Jun 03, 2008  01:27 +0100, Duane Griffin wrote:
> I'm looking at http://bugzilla.kernel.org/show_bug.cgi?id=9866, where
> the reporter is claiming that EXT3_TOPDIR_FL (chattr +T) is behaving
> incorrectly by being inherited from the parent. As mentioned in the
> bug, it also only seems to only make sense for directories but
> ext{2,3,4} is happy to set it on anything. It seems to me that the
> reporter is correct and the behaviour should be changed to prevent the
> flag being inherited and to limit it to directories only. If there is
> no disagreement I'll follow-up with patches accordingly.

Yes, this is a problem that was mentioned previously, and hasn't been
fixed yet.  The TOPDIR_FL shouldn't be inherited, similar to the
non-inheritance of INDEX_FL and EXTENTS_FL.

It could be argued pretty easily that inheriting flags is usually wrong,
and that we should instead specify which flags SHOULD be inherited,
instead of repeatedly fixing bugs like this.

Flags that I would propose should be inherited from directories to
regular files and subdirectories are: SECRM, UNRM, SYNC, APPEND, NODUMP,
NOATIME, COMPR, NOCOMPR, JOURNAL_DATA, NOTAIL, and DIRSYNC, EXTENTS.
I'm not sure what the semantics of IMMUTABLE on a directory are, whether
it is even possible to create a new file in such a directory, but by
principle of least surprise it should probably be inherited.

Flags that definitely do not make sense to be inherited are: DIRTY, ECOMPR,
INDEX, IMAGIC, TOPDIR, HUGE_FILE.

Flags that don't make sense to be set on non-file/dir inodes are: DIRTY,
ECOMPR, INDEX, SECRM, UNRM, SYNC, APPEND, COMPR, NOCOMPR, JOURNAL_DATA,
NOTAIL, DIRSYNC, TOPDIR, EXTENTS, HUGE_FILE (used for files > 2TB).

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/