linux-toradex.git/fs/dlm, branch v2.6.30.2

dlm: fix length calculation in compat code

2009-03-11T17:23:59+00:00

Using offsetof() to calculate name length does not work because
it does not produce consistent results with with structure packing.
This caused memcpy to corrupt memory by copying 4 extra bytes off
the end of the buffer on 64 bit kernels with 32 bit userspace
(the only case where this 32/64 compat code is used).

The fix is to calculate name length directly from the start instead
of trying to derive it later using count and offsetof.

Signed-off-by: David Teigland

dlm: ignore cancel on granted lock

2009-03-11T17:23:58+00:00

Return immediately from dlm_unlock(CANCEL) if the lock is
granted and not being converted; there's nothing to cancel.

Signed-off-by: David Teigland

dlm: clear defunct cancel state

2009-03-11T17:23:39+00:00

When a conversion completes successfully and finds that a cancel
of the convert is still in progress (which is now a moot point),
preemptively clear the state associated with outstanding cancel.
That state could cause a subsequent conversion to be ignored.

Also, improve the consistency and content of error and debug
messages in this area.

Signed-off-by: David Teigland

dlm: replace idr with hash table for connections

2009-03-11T17:20:58+00:00

Integer nodeids can be too large for the idr code; use a hash
table instead.

Signed-off-by: Christine Caulfield 
Signed-off-by: David Teigland

dlm: comment typo fixes

2009-01-28T18:56:07+00:00

Signed-off-by: Joe Perches 
Signed-off-by: David Teigland

dlm: use ipv6_addr_copy

2009-01-28T18:56:02+00:00

Signed-off-by: Joe Perches 
Signed-off-by: David Teigland

dlm: Change rwlock which is only used in write mode to a spinlock

2009-01-28T18:55:55+00:00

The ls_dirtbl[].lock was an rwlock, but since it was only used in write
mode a spinlock will suffice.

Signed-off-by: Steven Whitehouse 
Signed-off-by: David Teigland

dlm: initialize file_lock struct in GETLK before copying conflicting lock

2009-01-21T21:28:45+00:00

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 
Signed-off-by: David Teigland

dlm: fix plock notify callback to lockd

2009-01-21T21:28:45+00:00

We should use the original copy of the file_lock, fl, instead
of the copy, flc in the lockd notify callback.  The range in flc has
been modified by posix_lock_file(), so it will not match a copy of the
lock in lockd.

Signed-off-by: David Teigland

dlm: change rsbtbl rwlock to spinlock

2009-01-08T21:12:39+00:00

The rwlock is almost always used in write mode, so there's no reason
to not use a spinlock instead.

Signed-off-by: David Teigland