It would be better (and much simpler) to "modify" the file system to allow
a service inode to point to the inode of an executable. The executable could
then implment the file operations for open/close/read/write/seek and possibly
even IOCTL. Parameters passed to the executable could be the file handle of
the data file being referenced, and the PID of the process making the reference.
The executable would have access to additional information about the parent
process (UID/GID list).
The kernel wouldn't have to track anything, there would be less global
interaction with the kernel.
This could be a hook for providing database level access to data (passing
queries via IOCTL), simple read/write access to a database (using ioctl to
setup, then read/write to transfer the data). It could even be used to
implement custom auditing/journaling on a file-by-file basis.
-- ------------------------------------------------------------------------- Jesse I Pollard, II Email: pollard@cats-chateau.netAny opinions expressed are solely my own.
- 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/