kernel-ark/include/linux/lockd
Marc Eshel 9a8db97e77 knfsd: lockd: nfsd4: use same grace period for lockd and nfsd4
Both lockd and (in the nfsv4 case) nfsd enforce a "grace period" after reboot,
during which clients may reclaim locks from the previous server instance, but
may not acquire new locks.

Currently the lockd and nfsd enforce grace periods of different lengths.  This
may cause problems when we reboot a server with both v2/v3 and v4 clients.
For example, if the lockd grace period is shorter (as is likely the case),
then a v3 client might acquire a new lock that conflicts with a lock already
held (but not yet reclaimed) by a v4 client.

This patch calculates a lease time that lockd and nfsd can both use.

Signed-off-by: Marc Eshel <eshel@almaden.ibm.com>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-07-17 10:23:07 -07:00
..
bind.h knfsd: lockd: nfsd4: use same grace period for lockd and nfsd4 2007-07-17 10:23:07 -07:00
debug.h
lockd.h NLM: fix source address of callback to client 2007-07-10 23:40:49 -04:00
nlm.h Don't include linux/config.h from anywhere else in include/ 2006-04-26 12:56:16 +01:00
share.h [PATCH] lockd endianness annotations 2006-10-20 10:26:40 -07:00
sm_inter.h [PATCH] lockd endianness annotations 2006-12-13 09:05:52 -08:00
xdr4.h NLM: Fix sparse warnings 2007-05-14 19:33:46 -04:00
xdr.h [PATCH] lockd endianness annotations 2006-12-13 09:05:52 -08:00