> On Tuesday 16 October 2012, Jaegeuk Kim wrote: > > > > > > > > An xattr on the root inode that holds a list like this is something > > > > > that could be set at mkfs time, but then also updated easily by new > > > > > software packages that are installed... > > > > > > Yes, good idea. > > > > Likewise many file systems, f2fs also supports xattr as a configurable > > Kconfig option. > > If user disables the xattr feature, how can we do this? > > I can see three options here: > > * make the extension list feature dependent on xattr, and treat all files > the same if it's disabled. > > * put the list into the superblock instead. > > * fall back on a hardcoded list of extensions when the extended attribute > is not present or the feature is disabled. >
IMHO, we don't need to disable the extension list among the cases. So, as I described before, I propose the following options. * By default, mkfs stores an extension list in superblock, and f2fs simply uses it. * If users try to handle cold files by themselves, they can give a hint via the xattr interface. * Whenever they want not to use the default extension list, they can easily disable it by a mount option. > Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
