diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-04-11 16:48:44 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2010-04-26 07:47:53 -0700 |
| commit | 9c84e4813a02a219d61f61967d7058f2d8037d88 (patch) | |
| tree | 2d9d9aa2a465e30cda0fa984117bbe60004de705 /drivers/block/hd.c | |
| parent | a354226edbcd28cd1a55d0abbbbc9a703ba26f1c (diff) | |
| download | kernel-crypto-9c84e4813a02a219d61f61967d7058f2d8037d88.tar.gz kernel-crypto-9c84e4813a02a219d61f61967d7058f2d8037d88.tar.xz kernel-crypto-9c84e4813a02a219d61f61967d7058f2d8037d88.zip | |
NFSv4: fix delegated locking
commit 0df5dd4aae211edeeeb84f7f84f6d093406d7c22 upstream.
Arnaud Giersch reports that NFSv4 locking is broken when we hold a
delegation since commit 8e469ebd6dc32cbaf620e134d79f740bf0ebab79 (NFSv4:
Don't allow posix locking against servers that don't support it).
According to Arnaud, the lock succeeds the first time he opens the file
(since we cannot do a delegated open) but then fails after we start using
delegated opens.
The following patch fixes it by ensuring that locking behaviour is
governed by a per-filesystem capability flag that is initially set, but
gets cleared if the server ever returns an OPEN without the
NFS4_OPEN_RESULT_LOCKTYPE_POSIX flag being set.
Reported-by: Arnaud Giersch <arnaud.giersch@iut-bm.univ-fcomte.fr>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/block/hd.c')
0 files changed, 0 insertions, 0 deletions