From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Theodore Ts'o <tytso@mit.edu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Rob Browning <rlb@defaultvalue.org>,
Dave Chinner <david@fromorbit.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH] fs: xattr-based FS_IOC_[GS]ETFLAGS interface
Date: Tue, 7 Jan 2014 07:49:35 -0800 [thread overview]
Message-ID: <20140107154935.GA17609@infradead.org> (raw)
In-Reply-To: <20140107124831.GD16640@quack.suse.cz>
On Tue, Jan 07, 2014 at 01:48:31PM +0100, Jan Kara wrote:
> I have to say I'm not thrilled by the idea of juggling strings in
> userspace and in kernel to set a flag for an inode...
Nevermind the massive amounts of code that sit in the filesystem.
Although my recent ACL patches are the first step towards handling the
existing semantically overloaded xattrs in common code. Unless Al has
a valid reason to disagree I'd like to put a big NAK on adding any new
xattrs that aren't stored on disk as-is but provide magic functionality,
as they are pain to implement, maintain, and audit.
next prev parent reply other threads:[~2014-01-07 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 2:58 [RFC PATCH] fs: xattr-based FS_IOC_[GS]ETFLAGS interface Darrick J. Wong
2014-01-07 12:48 ` Jan Kara
2014-01-07 15:49 ` Christoph Hellwig [this message]
2014-01-07 17:04 ` Theodore Ts'o
2014-01-07 19:43 ` Darrick J. Wong
2014-01-07 19:59 ` Chris Mason
2014-01-07 22:02 ` Darrick J. Wong
2014-01-07 22:08 ` Chris Mason
2014-01-07 22:27 ` Theodore Ts'o
2014-01-07 22:04 ` [RFC PATCH v2] fs: new FS_IOC_[GS]ETFLAGS2 interface Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140107154935.GA17609@infradead.org \
--to=hch@infradead.org \
--cc=aurelien@aurel32.net \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rlb@defaultvalue.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).