[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201210171225.01511.arnd@arndb.de>
Date: Wed, 17 Oct 2012 12:25:01 +0000
From: Arnd Bergmann <arnd@...db.de>
To: Jaegeuk Kim <jaegeuk.kim@...il.com>
Cc: Jaegeuk Kim <jaegeuk.kim@...sung.com>,
"'Dave Chinner'" <david@...morbit.com>,
"'Vyacheslav Dubeyko'" <slava@...eyko.com>,
viro@...iv.linux.org.uk, "'Theodore Ts'o'" <tytso@....edu>,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
chur.lee@...sung.com, cm224.lee@...sung.com,
jooyoung.hwang@...sung.com
Subject: Re: [PATCH 11/16] f2fs: add inode operations for special inodes
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.
Arnd
--
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