Messages in this thread | | | From | mike.kupfer@sun ... | Subject | Re: [NFS] Re: Non-blocking lock requests during the grace period | Date | Mon, 18 Nov 2002 17:04:32 -0800 |
| |
>>>>> "Trond" == Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>>>>> " " == Juan Gomez <juang@us.ibm.com> writes:
>> (note that F_GETLK man page does not provide EAGAIN as a >> possible error code).
F_GETLK indicates a conflict by changing the arg struct to show the conflicting lock.
As for the original topic, I would hesitate before changing the client locking code to return EAGAIN just because the server is in its grace period. The "blocking" or "non-blocking" behavior is tied to what happens when there is already a lock that conflicts with the requested one. When the server is in the grace period, it's unknown as to whether there is already a lock that conflicts with the requested one.
Mike Kupfer mike.kupfer@sun.com Solaris File Sharing Speaking for myself, not for Sun.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |