07 Jan, 2011
1 commit
-
Delegations are per-inode, not per-nfs_client. When a server file
system is migrated, delegations on the client must be moved from the
source to the destination nfs_server. Make it easier to manage a
mount point's delegation list across a migration event by moving the
list to the nfs_server struct.Clean up: I added documenting comments to public functions I changed
in this patch. For consistency I added comments to all the other
public functions in fs/nfs/delegation.c.Signed-off-by: Chuck Lever
Signed-off-by: Trond Myklebust
23 Jun, 2010
1 commit
-
Signed-off-by: Trond Myklebust
11 Mar, 2010
1 commit
-
If the NFS_INO_REVAL_FORCED flag is set, that means that we don't yet have
an up to date attribute cache. Even if we hold a delegation, we must
put a GETATTR on the wire.Signed-off-by: Trond Myklebust
Cc: stable@kernel.org
06 Dec, 2009
2 commits
-
in NFSv4.1 the seqid part of a stateid in CB_RECALL must be 0
Signed-off-by: Alexandros Batsakis
Signed-off-by: Trond Myklebust -
For now the clients returns _all_ the delegations of the specificed type
it holdsSigned-off-by: Alexandros Batsakis
Signed-off-by: Trond Myklebust
03 Dec, 2009
1 commit
-
The nfsv4 state manager could potentially deadlock inside
__nfs_inode_return_delegation() if the server reboots, so that the calls to
nfs_msync_inode() end up waiting on state recovery to complete.Also ensure that if a server reboot or network partition causes us to have
to stop returning delegations, that NFS4CLNT_DELEGRETURN is set so that
the state manager can resume any outstanding delegation returns after it
has dealt with the state recovery situation.Finally, ensure that the state manager doesn't wait for the DELEGRETURN
call to complete. It doesn't need to, and that too can cause a deadlock.Signed-off-by: Trond Myklebust
24 Dec, 2008
6 commits
-
Signed-off-by: Trond Myklebust
-
If the client is not using a delegation, the right thing to do is to return
it as soon as possible. This helps reduce the amount of state the server
has to track, as well as reducing the potential for conflicts with other
clients.Signed-off-by: Trond Myklebust
-
Add a delegation cleanup phase to the state management loop, and do the
NFS4ERR_CB_PATH_DOWN recovery there.Signed-off-by: Trond Myklebust
-
Add a flag to mark delegations as requiring return, then run a garbage
collector. In the future, this will allow for more flexible delegation
management, where delegations may be marked for return if it turns out
that they are not being referenced.Signed-off-by: Trond Myklebust
-
Signed-off-by: Trond Myklebust
-
When we can update_open_stateid(), we need to be certain that we don't
race with a delegation return. While we could do this by grabbing the
nfs_client->cl_lock, a dedicated spin lock in the delegation structure
will scale better.Signed-off-by: Trond Myklebust
30 Jan, 2008
1 commit
-
Otherwise, there is a potential deadlock if the last dput() from an NFSv4
close() or other asynchronous operation leads to nfs_clear_inode calling
the synchronous delegreturn.Signed-off-by: Trond Myklebust
11 Jul, 2007
4 commits
-
Signed-off-by: Trond Myklebust
-
Signed-off-by: Trond Myklebust
-
There appear to be some rogue servers out there that issue multiple
delegations with different stateids for the same file. Ensure that when we
return delegations, we do so on a per-stateid basis rather than a per-file
basis.Signed-off-by: Trond Myklebust
-
Signed-off-by: Trond Myklebust
23 Sep, 2006
1 commit
-
Rename struct nfs4_client to struct nfs_client so that it can become the basis
for a general client record for NFS2 and NFS3 in addition to NFS4.Signed-Off-By: David Howells
Signed-off-by: Trond Myklebust
21 Mar, 2006
1 commit
-
In the case where we hold a delegation stateid, use that in for inside
SETATTR calls.Signed-off-by: Trond Myklebust
07 Jan, 2006
2 commits
-
According to RFC3530 we're supposed to cache the change attribute
at the time the client receives a write delegation.
If the inode is clean, a CB_GETATTR callback by the server to the
client is supposed to return the cached change attribute.
If, OTOH, the inode is dirty, the client should bump the cached
change attribute by 1.Signed-off-by: Trond Myklebust
-
Signed-off-by: Trond Myklebust
05 Nov, 2005
1 commit
-
Delegations allow us to cache posix and BSD locks, however when the
delegation is recalled, we need to "flush the cache" and send
the cached LOCK requests to the server.This patch sets up the mechanism for doing so.
Signed-off-by: Trond Myklebust
19 Oct, 2005
1 commit
-
Signed-off-by: Trond Myklebust
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
