Glibc 2.20 released

Posted Sep 9, 2014 14:24 UTC (Tue) by bfields (subscriber, #19510)
In reply to: Glibc 2.20 released by nix
Parent article: Glibc 2.20 released

Well, it's a new kind of lock. You don't want this sort of lock on the client side to turn into the old form of POSIX lock on the server end, or vice versa.

I don't see a problem.

The POSIX/BSD problem arises because the two types of locks don't normally conflict with each other, but are forced to on NFS because they must be represented as the same type of lock.

But POSIX and the new open file description locks *do* conflict with each other (see a recent copy of the fcntl(2) man page), so it's simple enough to represent both over the same lock protocol.

So the protocol will need updating. (Since it needs updating to understand that POSIX locks exist at all, why not do both at once! :) )

Note that NFS locking is POSIX-like (in particular, it supports byte ranges), so it's BSD locks that would need to be added.

Glibc 2.20 released

Posted Sep 17, 2014 18:26 UTC (Wed) by nix (subscriber, #2304) [Link]

But POSIX and the new open file description locks *do* conflict with each other (see a recent copy of the fcntl(2) man page), so it's simple enough to represent both over the same lock protocol.

True. I don't know what I was thinking. (Of couse, they'll still wrongly conflict with fnctl() locks...)