Hi Jeff,
I've been looking a bit at the fcntl() documentation of traditional
(F_SETLK) record locking, and a question just jumped out at me. Is
it worth considering some future-proofing in the design of OFD locks
("open file description locks", formerly known as "file-private locks")?
What I am thinking of here is that on some systems, the traditional
'struct flock' has a nonstandard field, l_sysid, that is used on F_GETLK
to identify the remote system on which a lock is held. Should the design
of OFD locks allow for such a field (now, or in the future), which might
be useful in the context of locking on network file systems such as NFS.
Put more simply, should the new OFD locking system be using a new
structure for describing locks, rather than the traditional 'struct
flock'? Defining a new structure, might be useful to allow for
future extensions to the API.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
