Jeff Layton 20d5a39929 dlm: initialize file_lock struct in GETLK before copying conflicting lock
dlm_posix_get fills out the relevant fields in the file_lock before
returning when there is a lock conflict, but doesn't clean out any of
the other fields in the file_lock.

When nfsd does a NFSv4 lockt call, it sets the fl_lmops to
nfsd_posix_mng_ops before calling the lower fs. When the lock comes back
after testing a lock on GFS2, it still has that field set. This confuses
nfsd into thinking that the file_lock is a nfsd4 lock.

Fix this by making DLM reinitialize the file_lock before copying the
fields from the conflicting lock.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
2009-01-21 15:28:45 -06:00
..
2008-12-25 11:40:09 +11:00
2008-11-14 10:39:25 +11:00
2009-01-09 21:05:21 +00:00
2009-01-07 17:38:31 -05:00
2008-10-17 02:38:36 +11:00
2009-01-05 11:54:27 -05:00
2009-01-08 08:31:15 -08:00
2009-01-05 11:54:28 -05:00
2008-12-04 17:16:36 +11:00
2008-12-31 18:07:43 -05:00
2009-01-03 11:45:54 -08:00
2009-01-06 15:59:09 -08:00