Christoph, On 04/21/2014 06:09 PM, Christoph Hellwig wrote: > On Mon, Apr 21, 2014 at 04:23:54PM +0200, Michael Kerrisk (man-pages) wrote: >> >> There's at least two problems to solve here: >> >> 1) "File private locks" is _meaningless_ as a term. Elsewhere >> (http://thread.gmane.org/gmane.network.samba.internals/76414/focus=1685376), > > It's indeed not a very good choice, but the new name is even worse. > Just call them non-broken locks? :) Or not give them a name an just > append a 2 to the fcntls? :) As Jeff points out, they must have a name, or we can't have sensible discussions about them ;-). >> 2) The new API constants (F_SETLKP, F_SETLKPW, F_GETLKP) have names >> that are visually very close to the traditional POSIX lock names >> (F_SETLK, F_SETLKW, F_GETLK). That's an accident waiting to happen >> when someone mistypes in code and/or misses such a misttyping >> when reading code. That really must be fixed. > > I don't think so. They also should have a name very similar because > they have the same semantics with a major bug fixed. In fact I can't > think of anyone who would actually want the old behavior. They should have a name that is similar, but not so similar that one is easily confused for the other. Some people will inevitably want the other behavior. Other people will be working on alternatively legacy and new applications. We should choose some constant names that minimize the chance of silly mistakes. Names that differ by just a single letter (in one case, inside the name) are a poor choice from that perspective. But, solving the naming of the constants is somewhat orthogonal to solving the name of the entity. At the least let's have something more visually distinctive, even if we stay with the current terminology. (See my other mail, just sent.) 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
