From: Andreas Dilger <adilger@turbolabs.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Alexander Viro <viro@math.psu.edu>, Andi Kleen <ak@suse.de>,
Andreas Gruenbacher <ag@bestbits.at>,
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: Wed, 14 Nov 2001 23:01:34 -0700 [thread overview]
Message-ID: <20011114230134.A5739@lynx.no> (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> <20011113062711.A1912@wotan.suse.de> <20011115160853.N588010@wobbly.melbourne.sgi.com>
In-Reply-To: <20011115160853.N588010@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Thu, Nov 15, 2001 at 04:08:53PM +1100
On Nov 15, 2001 16:08 +1100, Nathan Scott wrote:
> + if (ops) {
> + if (flags & EA_CREATE) {
> + if (ops->create)
> + error = ops->create(i, name, value, size);
> + }
> + else if (flags & EA_REPLACE) {
> + if (ops->replace)
> + error = ops->replace(i, name, value, size);
> + }
> + else if (flags & EA_REMOVE) {
> + if (ops->remove)
> + error = ops->remove(i, name);
> + }
> + else if (ops->set)
> + error = ops->set(i, name, value, size);
> + }
> + int (*create) (struct inode *, char *, void *, size_t);
> + int (*replace) (struct inode *, char *, void *, size_t);
> + int (*set) (struct inode *, char *, void *, size_t);
What is the distinction between "set" and "replace" or "set" and "create"?
Is it analogous to open(,O_CREAT|O_EXCL)? If so, why are there not just
flags to distinguish the two, but also separate VFS operations?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-15 6:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 9:08 [RFC][PATCH] " 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
2001-11-15 5:08 ` Nathan Scott
2001-11-15 6:01 ` Andreas Dilger [this message]
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=20011114230134.A5739@lynx.no \
--to=adilger@turbolabs.com \
--cc=ag@bestbits.at \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®