litmus-rt.git - The LITMUS^RT kernel.

	Commit message (Collapse)	Author	Age
*	NFS: Add an asynchronous delegreturn operation for use in nfs_clear_inode	Trond Myklebust	2008-01-30
\| \| \| \| \| \| \| \|	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 <Trond.Myklebust@netapp.com>
*	NFSv4: Use RCU to protect delegations	Trond Myklebust	2007-07-10
\| \| \| \|	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFSv4: Support recalling delegations by stateid part 2	Trond Myklebust	2007-07-10
\| \| \| \|	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFSv4: Support recalling delegations by stateid	Trond Myklebust	2007-07-10
\| \| \| \| \| \| \| \| \|	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 <Trond.Myklebust@netapp.com>
*	NFSv4: Cleanup: pass the nfs_open_context to open recovery code	Trond Myklebust	2007-07-10
\| \| \| \|	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFS: Rename struct nfs4_client to struct nfs_client	David Howells	2006-09-22
\| \| \| \| \| \| \| \|	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 <dhowells@redhat.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFSv4: Send the delegation stateid for SETATTR calls	Trond Myklebust	2006-03-20
\| \| \| \| \| \| \|	In the case where we hold a delegation stateid, use that in for inside SETATTR calls. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec	Trond Myklebust	2006-01-06
\| \| \| \| \| \| \| \| \| \| \|	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 <Trond.Myklebust@netapp.com>
*	NFSv4: Send RENEW requests to the server only when we're holding state	Trond Myklebust	2006-01-06
\| \| \| \|	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFSv4: Recover locks too when returning a delegation	Trond Myklebust	2005-11-04
\| \| \| \| \| \| \| \| \| \|	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 <Trond.Myklebust@netapp.com>
*	NFSv4: Return delegation upon rename or removal of file.	Trond Myklebust	2005-10-18
\| \| \| \|	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds	2005-04-16
	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!