From: Chris Mason <mason@suse.com>
To: Jan Harkes <jaharkes@cs.cmu.edu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] icreate-7
Date: 02 May 2002 10:22:36 -0400 [thread overview]
Message-ID: <1020349356.1510.36.camel@tiny> (raw)
In-Reply-To: <20020501225904.GA16058@mentor.odyssey.cs.cmu.edu>
On Wed, 2002-05-01 at 18:59, Jan Harkes wrote:
> Another day another update,
>
> Fixed the documentation error, thanks Kai, and tried to follow Al's
> advice by not including ino separately, but using *(ino_t *)data for
> the inode hash calculation. Don't really like it myself, but who am
> I to argue and it might end up making life a bit simpler for NFS and
> Intermezzo because we end up having only a single identifier for an
> object. OTOH, if everything switches to icreate the filesystems will
> have to provide a lookup mechanism through export_ops.
Hmmm, a void * implies the FS can put whatever garbage it wants there,
I'd rather see the FS cast its own icreate_args struct into one that
specifies what the FS is expected to include.
Something like this:
struct icreate_args {
ino_t ino;
}
and
struct foofs_create_args {
ino_t ino;
< other foofs stuff >
}
struct inode *icreate(struct super_block *sb, unsigned long ino,
int (*test)(struct inode *, void *),
int (*set)(struct inode *, void *),
struct icreate_args *);
-chris
next prev parent reply other threads:[~2002-05-02 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 22:59 [PATCH] icreate-7 Jan Harkes
2002-05-01 23:58 ` Anton Altaparmakov
2002-05-02 0:19 ` Jan Harkes
2002-05-02 14:22 ` Chris Mason [this message]
2002-05-03 20:26 ` Jan Harkes
2002-05-03 20:37 ` Jan Harkes
2002-05-05 0:49 ` [PATCH] icreate-8 [1/2] Jan Harkes
2002-05-05 0:52 ` [PATCH] icreate-8 [2/2] Jan Harkes
2002-05-05 1:20 ` [PATCH] icreate-8 [3/2] Jan Harkes
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=1020349356.1510.36.camel@tiny \
--to=mason@suse.com \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.