summaryrefslogtreecommitdiff
path: root/fs/nfsd/blocklayout.c
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2015-06-08 10:11:46 +0200
committerStefan Agner <stefan.agner@toradex.com>2015-06-08 10:11:46 +0200
commit17b63cad14be4b3b407451da0e10a688b67b0c83 (patch)
treed3ce41b603d1de3d7c710ef9c515de70441b6cd4 /fs/nfsd/blocklayout.c
parentafd1ef6b14dd6ba9d2f0d09f99a21c610a2d2c09 (diff)
parentbe4cb235441a691ee63ba5e00843a9c210be5b8a (diff)
Merge tag 'v4.0.5' into toradex_vf_4.0-next
This is the 4.0.5 stable release
Diffstat (limited to 'fs/nfsd/blocklayout.c')
-rw-r--r--fs/nfsd/blocklayout.c11
1 files changed, 11 insertions, 0 deletions
diff --git a/fs/nfsd/blocklayout.c b/fs/nfsd/blocklayout.c
index 03d647bf195d..cdefaa331a07 100644
--- a/fs/nfsd/blocklayout.c
+++ b/fs/nfsd/blocklayout.c
@@ -181,6 +181,17 @@ nfsd4_block_proc_layoutcommit(struct inode *inode,
}
const struct nfsd4_layout_ops bl_layout_ops = {
+ /*
+ * Pretend that we send notification to the client. This is a blatant
+ * lie to force recent Linux clients to cache our device IDs.
+ * We rarely ever change the device ID, so the harm of leaking deviceids
+ * for a while isn't too bad. Unfortunately RFC5661 is a complete mess
+ * in this regard, but I filed errata 4119 for this a while ago, and
+ * hopefully the Linux client will eventually start caching deviceids
+ * without this again.
+ */
+ .notify_types =
+ NOTIFY_DEVICEID4_DELETE | NOTIFY_DEVICEID4_CHANGE,
.proc_getdeviceinfo = nfsd4_block_proc_getdeviceinfo,
.encode_getdeviceinfo = nfsd4_block_encode_getdeviceinfo,
.proc_layoutget = nfsd4_block_proc_layoutget,