From: Ronald E Bretschneider (bret@us.ibm.com)
Date: 07/07/03-11:24:41 AM Z
Message-ID: <OF88BC2AD4.D5B6D65B-ON88256D5C.0059D037@us.ibm.com> From: Ronald E Bretschneider <bret@us.ibm.com> Subject: [nfsv4] (no subject) Date: Mon, 7 Jul 2003 09:24:41 -0700 Perhaps you can help me understand this, I am confused. The NFS V4 lock interface contains the locker4 structure which is switched based on a bit new_lock_owner. The client will use some test to determine whether it has presented this lockowner to the server. Perhaps this test is in the form of "if this is the first lock request from this user-process for this open". If it has not presented this lockowner to the server, it builds the open_to_lock_owner4 structure, otherwise it builds the exist_lock_owner4 structure. However, on the server side, my locking code needs to determine what the format of the locker4 structure is. Certainly if the new_lock_owner bit was part of the interface, I would know the format. But it does not seem that this bit is a parameter in the interface. Certainly if I could look at the lock_owner value which was being passed, I could know whether I had seen this lock owner previously, but to look at this field, I would already have to know the format. I could even infer the format if the lock_stateid and the open_stateid values were at the same offset in the structure (I might have a flag in the stateid which differentiated open and lock stateids), but they are at different offsets in the structure. So, what is it that I am missing? How does my server lock code know the format of the locker4 structure? thanks, Ron _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4
This archive was generated by hypermail 2.1.2 : 03/04/05-02:12:33 AM Z CST