NFSv4: Respect the server imposed limit on how many changes we may cache
authorTrond Myklebust <trond.myklebust@primarydata.com>
Sat, 5 Sep 2015 23:06:58 +0000 (19:06 -0400)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Mon, 7 Sep 2015 16:36:17 +0000 (12:36 -0400)
commit5445b1fbd123420bffed5e629a420aa2a16bf849
treedaea751ed98d60c445017472d6f2545452e0224a
parent7d160a6c462c2c690e074c173b43aad7204049ad
NFSv4: Respect the server imposed limit on how many changes we may cache

The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/delegation.c
fs/nfs/delegation.h
fs/nfs/file.c
fs/nfs/internal.h
fs/nfs/nfs4file.c