> For a filesystem-initiated IOCTL, there is indeed no user endpoint. In that
> case, pass in the value NONE. The user_endpt parameter is only used in rare
> cases where the IOCTL could not conceivably have been initiated by a file
> system server anyway. And yes, I am horribly behind with writing
> documentation.. :(
Ok, thanks a lot for this clarification.
I have an additional question, looking at the Minix FS code: the
device identifier (dev_t) is used thoroughly within the
implementation, for example when looking for a cached inode
(find_inode), dev is specified and compare against the inode's i_dev
I do not get how the devices could not match, as it seems there is one
instance of FS server for each mounted partition (BTW, I'm not sure if
this implementation choice is actually documented on the Minix web
site). Is this a left-over piece of code from a previous version of
Minix, or have I actually missed something here?
In order words, fs_dev and superblock are global, unique in a given
mfs instance, so why is dev_t stored within each inode?
BTW, I think the "register" compiler hints could be safely removed as
I think they are ignored by all modern compilers.