linux - linux

	Commit message (Collapse)	Author	Age	Files	Lines
*	locks,lockd: fix race in nlmsvc_testlock	Andy Adamson	2006-03-20	1	-4/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	posix_test_lock() returns a pointer to a struct file_lock which is unprotected and can be removed while in use by the caller. Move the conflicting lock from the return to a parameter, and copy the conflicting lock. In most cases the caller ends up putting the copy of the conflicting lock on the stack. On i386, sizeof(struct file_lock) appears to be about 100 bytes. We're assuming that's reasonable. Signed-off-by: Andy Adamson <andros@citi.umich.edu> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFS: add I/O performance counters	Chuck Lever	2006-03-20	1	-11/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Invoke the byte and event counter macros where we want to count bytes and events. Clean-up: fix a possible NULL dereference in nfs_lock, and simplify nfs_file_open. Test-plan: fsx and iozone on UP and SMP systems, with and without pre-emption. Watch for memory overwrite bugs, and performance loss (significantly more CPU required per op). Signed-off-by: Chuck Lever <cel@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFS: Avoid races between writebacks and truncation	Trond Myklebust	2006-03-20	1	-0/+13
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Currently, there is no serialisation between NFS asynchronous writebacks and truncation at the page level due to the fact that nfs_sync_inode() cannot lock the pages that it is about to write out. This means that it is possible to be flushing out data (and calling something like set_page_writeback()) while the page cache is busy evicting the page. Oops... Use the hooks provided in try_to_release_page() to ensure that dirty pages are always written back to storage before we evict them. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	[PATCH] fix posix lock on NFS	ASANO Masahiro	2005-12-22	1	-1/+2
\| \| \| \| \| \| \| \| \| \|	NFS client prevents mandatory lock, but there is a flaw on it; Locks are possibly left if the mode is changed while locking. This permits unlocking even if the mandatory lock bits are set. Signed-off-by: ASANO Masahiro <masano@tnes.nec.co.jp> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	NFS: Fix another O_DIRECT race	Trond Myklebust	2005-12-20	1	-19/+4
\| \| \| \| \| \| \|	Ensure we call unmap_mapping_range() and sync dirty pages to disk before doing an NFS direct write. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFS: Optimise attribute revalidation on close().	Trond Myklebust	2005-10-28	1	-2/+2
\| \| \| \| \| \| \|	Only force a getattr in nfs_file_flush() if the attribute cache is stale. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	NFS: Fix up a race in the NFS implementation of GETLK	Trond Myklebust	2005-10-18	1	-9/+18
\| \| \| \| \| \| \|	...and fix a memory corruption bug due to improper use of memcpy() on a struct file_lock. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	[PATCH] NFS: Fix cache consistency races	Trond Myklebust	2005-10-17	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \| \|	If the data cache has been marked as potentially invalid by nfs_refresh_inode, we should invalidate it rather than assume that changes are due to our own activity. Also ensure that we always start with a valid cache before declaring it to be protected by a delegation. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	[PATCH] NFS: split nfsi->flags into two fields	Chuck Lever	2005-08-18	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Certain bits in nfsi->flags can be manipulated with atomic bitops, and some are better manipulated via logical bitmask operations. This patch splits the flags field into two. The next patch introduces atomic bitops for one of the fields. Test plan: Millions of fsx ops on SMP clients. Signed-off-by: Chuck Lever <cel@netapp.com> Cc: Trond Myklebust <trond.myklebust@fys.uio.no> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	[PATCH] NFS: Ensure that fstat() always returns the correct mtime	Trond Myklebust	2005-06-22	1	-6/+22
\| \| \| \| \| \|	Even if the file is open for writes. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	[PATCH] NFS: Cleanup of caching code, and slight optimization of writes.	Trond Myklebust	2005-06-22	1	-3/+9
\| \| \| \| \| \| \|	Unless we're doing O_APPEND writes, we really don't care about revalidating the file length. Just make sure that we catch any page cache invalidations. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	[PATCH] NFS: Add support for NFSv3 ACLs	Andreas Gruenbacher	2005-06-22	1	-0/+12
\| \| \| \| \| \| \| \| \| \| \| \| \|	This adds acl support fo nfs clients via the NFSACL protocol extension, by implementing the getxattr, listxattr, setxattr, and removexattr iops for the system.posix_acl_access and system.posix_acl_default attributes. This patch implements a dumb version that uses no caching (and thus adds some overhead). (Another patch in this patchset adds caching as well.) Signed-off-by: Andreas Gruenbacher <agruen@suse.de> Acked-by: Olaf Kirch <okir@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
*	[PATCH] NFS: Ensure that we revalidate the cached file length for ↵	Trond Myklebust	2005-06-13	1	-1/+41
\| \| \| \| \| \| \| \| \| \|	llseek(SEEK_END) This fixes a data corruption error for mail delivery applications that expect to be able to do posix locking and then append writes on NFS. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds	2005-04-17	1	-0/+484
	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!