From: "Trond Myklebust" <[EMAIL PROTECTED]>
> ??? It'll be a completely useless form of lock if programs can end up
> blocking forever on a set of (from their perspective) valid
> operations.

Some would argue that if it could lead to deadlock, then it's not a valid
set of operations.

That applies, of course, only to applications.  Servers acting on behalf of
multiple applications might end up issuing such an "erroneous" sequence of
operations, and it would be bad for a server thread to lock up as a result.
In that case, wouldn't it be better to implement asynchronous or
non-blocking forms of the locking calls than to insist on deadlock
detection?  DD is a notoriously aggravating piece of code to implement and
maintain, and it's a complete waste of time for applications that have
already taken steps to ensure deadlock-free operation.  The only
applications that benefit from DD are the broken ones.

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]

Reply via email to