Folks, it seems that now I have something that can be considered as a very
first attempt to implement proper file handles on a per-fs basis.
The main idea behind all this stuff is that it should be up to each filesystem to
decide whether it wants to be exportable or not. And if yes -- provide
strong invariants for external representation of its objects to the knfsd
module via two (hope!) well defined procedures:
fhandle_to_dentry()
dentry_to_fhandle()
As an example I took ext2 and hacked around namei.c. Take a look at it and
*please* express what do you think about the approach in general ( not
the coding style ;).
Now for the implementation details:
0. include/linux/fs.h:
just a few declarations.
1. knfsd part:
1.1. export.c: as I've already said an fs is said to be exportable iff
it provides fhandle_to_dentry & dentry_to_fhandle.
1.2. nfsfh.c: a lot of changes and not only in interface but also
in how subtrees are being checked. Trond, please take a look at
this beast ( it is from your forest ;). I'm asking because this
part, I mean knfsd, is pretty independent and should be purified
before we will start hacking filesystems.
2. ext2 ( but this will spread to any fs that we would like to export )
2.1. namei.c: well, this is a central part of all this PACTH. Thus
if you think you have something to say -- do it. Also keep in
mind that stuff like that will go to every fs that would like
to be exportable.
For those of you who feel to be a bit out of context I've attached a few
e-mails that may help.
Thanks,
Roman.
P.S. Almost forget to metion: the PATCH is against 2.4.0-test1-ac18.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:11 EST