203 Commits

Author	SHA1	Message	Date
Andrew Tridgell	43a80e1d83	r3031: added support for lock cancelation, which effectively just triggers an early lock timeout ... added support for more of the bizarre special lock offset semantics of w2k3 (This used to be commit d5bfc910b1)	2007-10-10 13:00:00 -05:00
Andrew Tridgell	d0cc571e30	r3029: implemented byte range lock timeouts. ... This adds a pvfs_wait_message() routine which uses the new messaging system, event timers and talloc destructors to give a nice generic async event handling system with a easy to use interface. The extensions to pvfs_lock.c are based on calls to pvfs_wait_message() routines. We now pass all of our smbtorture locking tests, although while writing this code I have thought of some additonal tests that should be added, particularly for lock cancel operations. I'll work on that soon. This commit also extends the smbtorture lock tests to test the rather weird 0xEEFFFFFF locking semantics that I have discovered in win2003. Win2003 treats the 0xEEFFFFFF boundary as special, and will give different error codes on either side of it. Locks on both sides are allowed, the only difference is which error code is given when a lock is denied. Anyone like to hazard a guess as to why? It has me stumped. (This used to be commit 4395c0557a)	2007-10-10 13:00:00 -05:00
Andrew Tridgell	fef617c31b	r3012: added initial support for byte range locking in the posix vfs. This is ... enough for us to pass locktest, but does not yet support lock timeouts and some of the other esoteric features. (This used to be commit 58a92abd88)	2007-10-10 12:59:57 -05:00