From: Andi Kleen <ak@suse.de>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andreas Gruenbacher <ag@bestbits.at>,
Nathan Scott <nathans@sgi.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@oss.sgi.com
Subject: Re: [RFC][PATCH] VFS interface for extended attributes
Date: Tue, 13 Nov 2001 06:27:11 +0100 [thread overview]
Message-ID: <20011113062711.A1912@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0111121152410.14344-100000@moses.parsec.at> <Pine.GSO.4.21.0111121207530.21825-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0111121207530.21825-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Mon, Nov 12, 2001 at 07:32:18PM -0500
On Mon, Nov 12, 2001 at 07:32:18PM -0500, Alexander Viro wrote:
> Which means that converting permission() to vfsmount/dentry should be
> done first. And that's not hard to do.
It's just messy as it will require changes in all file systems.
> Sorry, folks, but idea of private extendable syscall table (per-filesystem,
> no less) doesn't look like a good thing. That's _the_ reason why ioctl()
> is bad.
Unless I'm badly misreading the patch the op switch() is fixed in VFS mapping
to clearly defined inode operations. It is not extensible per filesystem.
Arguably they could be split into individual syscalls, but it looks not more
like cosmetics at this point.
-Andi
next prev parent reply other threads:[~2001-11-13 5:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 9:08 [RFC][PATCH] extended attributes Tim R.
2001-11-11 10:50 ` Nathan Scott
2001-11-12 1:57 ` Anton Altaparmakov
2001-11-12 3:20 ` Nathan Scott
2001-11-12 6:21 ` [RFC][PATCH] VFS interface for " Nathan Scott
2001-11-12 6:47 ` Alexander Viro
2001-11-12 11:39 ` Andreas Gruenbacher
2001-11-13 0:32 ` Alexander Viro
2001-11-13 5:27 ` Andi Kleen [this message]
2001-11-15 5:08 ` Nathan Scott
2001-11-15 6:01 ` Andreas Dilger
2001-11-15 23:18 ` Nathan Scott
2001-12-03 0:07 ` Daniel Phillips
2001-12-03 0:54 ` Nathan Scott
2001-12-03 14:52 ` Daniel Phillips
2001-12-03 23:14 ` Nathan Scott
2001-11-13 0:47 ` Anton Altaparmakov
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=20011113062711.A1912@wotan.suse.de \
--to=ak@suse.de \
--cc=ag@bestbits.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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