linux - Linux Kernel (branches are rebased on master from time to time)

Age	Commit message (Collapse)	Author	Files	Lines
2006-09-22	NFS: Rename struct nfs4_client to struct nfs_client	David Howells	1	-5/+5
	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>
2006-03-20	NFSv4: Send the delegation stateid for SETATTR calls	Trond Myklebust	1	-0/+1
	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>
2006-01-06	NFSv4: Ensure change attribute returned by GETATTR callback conforms to spec	Trond Myklebust	1	-0/+1
	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>
2006-01-06	NFSv4: Send RENEW requests to the server only when we're holding state	Trond Myklebust	1	-0/+1
	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
2005-11-04	NFSv4: Recover locks too when returning a delegation	Trond Myklebust	1	-0/+1
	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>
2005-10-18	NFSv4: Return delegation upon rename or removal of file.	Trond Myklebust	1	-1/+15
	Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
2005-04-16	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds	1	-0/+57
	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!