However, while looking though the code it occured to me that all the
places where generic code is run if there isn't a function provided by
a vfs, should really be split off as seperate functions (like
generic_read already is). This way a fs can chose to call the
"generic code" possibly as part of it's operation.
e.g. it may call the the generic permission code after dealing with
some weird fs specific permissions checking. This would also make
lofs much easier, as half the battle appears to be working out what to
do if an inode doesn't have a particular function (one of return an
error, or do some generic code usually).
Mind you I don't really want to wish this job on anyone, it is tedious
(and dangerous if you arn't a vfs expert).
Am I being stupid or should this be done sometime...
-- Jon Peatfield, DAMTP, Computer Officer, University of Cambridge Telephone: +44 1223 3 37852 Mail: J.S.Peatfield@damtp.cam.ac.uk