26 Sep, 2006
2 commits
-
Based on patch from Frank van Maarseveen , but
extended.Signed-off-by: Andi Kleen
-
If the timeout of an autofs mount is set to zero then umounts are disabled.
This works fine, however the kernel module checks the expire timeout and
goes no further if it is zero. This is not the right thing to do at
shutdown as the module is passed an option to expire mounts regardless of
their timeout setting.This patch allows autofs to honor the force expire option.
Signed-off-by: Ian Kent
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
25 Sep, 2006
28 commits
-
With this, we don't need to pass an additional struct with function pointer.
Now that the callbacks are fully used, comment the remaining API.
Signed-off-by: Mark Fasheh
-
Have ocfs2_process_blocked_lock() call ocfs2_generic_unblock_lock(), which
gets to be ocfs2_unblock_lock() now that it's the only possible unblock
function.Remove the ->unblock() callback from the structure, and all lock type
specific unblock functions.Signed-off-by: Mark Fasheh
-
This way lock types don't have to manually pass it to
ocfs2_generic_unblock_lock().Signed-off-by: Mark Fasheh
-
The meta data unblocking code no longer needs ocfs2_do_unblock_meta() or
ocfs2_can_downconvert_meta_lock(), so remove them.Signed-off-by: Mark Fasheh
-
Fill in the ->check_downconvert and ->set_lvb callbacks with meta data
specific operations and switch ocfs2_unblock_meta() to call
ocfs2_generic_unblock_lock()Signed-off-by: Mark Fasheh
-
This allows a lock type to set the value block before downconvert.
Signed-off-by: Mark Fasheh
-
This will allow lock types to force a requeue of a lock downconvert.
Signed-off-by: Mark Fasheh
-
Tidy up the exit path a bit too.
Signed-off-by: Mark Fasheh
-
Allow a lock type to specifiy whether it makes use of the LVB. The only type
which does this right now is the meta data lock. This should save us some
space on network messages since they won't have to needlessly transmit value
blocks.Signed-off-by: Mark Fasheh
-
There is extremely little difference between the two now. We can remove the
callback from ocfs2_lock_res_ops as well.Signed-off-by: Mark Fasheh
-
Will be used to find the ocfs2_super structure from a given lockres.
Signed-off-by: Mark Fasheh
-
This was always defined to the same function in all locks, so clean things
up by removing and passing ocfs2_unlock_ast() directly to the DLM.Signed-off-by: Mark Fasheh
-
There is extremely little difference between the two now. We can remove the
callback from ocfs2_lock_res_ops as well.Signed-off-by: Mark Fasheh
-
Use of the refresh mechanism is lock-type wide, so move knowledge of that to
the ocfs2_lock_res_ops structure.Signed-off-by: Mark Fasheh
-
OCFS2 puts inode meta data in the "lock value block" provided by the DLM.
Typically, i_generation is encoded in the lock name so that a deleted inode
on and a new one in the same block don't share the same lvb.Unfortunately, that scheme means that the read in ocfs2_read_locked_inode()
is potentially thrown away as soon as the meta data lock is taken - we
cannot encode the lock name without first knowing i_generation, which
requires a disk read.This patch encodes i_generation in the inode meta data lvb, and removes the
value from the inode meta data lock name. This way, the read can be covered
by a lock, and at the same time we can distinguish between an up to date and
a stale LVB.This will help cold-cache stat(2) performance in particular.
Since this patch changes the protocol version, we take the opportunity to do
a minor re-organization of two of the LVB fields.Signed-off-by: Mark Fasheh
-
When i_generation is removed from the lockname, this will help us determine
whether a meta data lvb has information that is in sync with the local
struct inode.Signed-off-by: Mark Fasheh
-
lvb_version doesn't need to be a whole 32 bits. Make it an 8 bit field to
free up some space. This should be backwards compatible until we use one of
the fields, in which case we'd bump the lvb version anyway.Signed-off-by: Mark Fasheh
-
We can't use LKM_LOCAL for new dentry locks because an unlink and subsequent
re-create of a name/inode pair may result in the lock still being mastered
somewhere in the cluster.Signed-off-by: Mark Fasheh
-
Make use of FS_RENAME_DOES_D_MOVE to avoid a race condition that can occur
during ->rename() if we d_move() outside of the parent directory cluster
locks, and another node discovers the new name (created during the rename)
and unlinks it. d_move() will unconditionally rehash a dentry - which will
leave stale data in the system.Signed-off-by: Mark Fasheh
-
Some file systems want to manually d_move() the dentries involved in a
rename. We can do this by making use of the FS_ODD_RENAME flag if we just
have nfs_rename() unconditionally do the d_move(). While there, we rename
the flag to be more descriptive.OCFS2 uses this to protect that part of the rename operation with a cluster
lock.Signed-off-by: Mark Fasheh
Cc: Trond Myklebust
Cc: Al Viro
Cc: Christoph Hellwig
Signed-off-by: Andrew Morton -
This is unused now.
Signed-off-by: Mark Fasheh
-
Actually replace the vote calls with the new dentry operations. Make any
necessary adjustments to get the scheme to work.Signed-off-by: Mark Fasheh
-
Replace the dentry vote mechanism with a cluster lock which covers a set
of dentries. This allows us to force d_delete() only on nodes which actually
care about an unlink.Every node that does a ->lookup() gets a read only lock on the dentry, until
an unlink during which the unlinking node, will request an exclusive lock,
forcing the other nodes who care about that dentry to d_delete() it. The
effect is that we retain a very lightweight ->d_revalidate(), and at the
same time get to make large improvements to the average case performance of
the ocfs2 unlink and rename operations.This patch adds the higher level API and the dentry manipulation code.
Signed-off-by: Mark Fasheh
-
Replace the dentry vote mechanism with a cluster lock which covers a set
of dentries. This allows us to force d_delete() only on nodes which actually
care about an unlink.Every node that does a ->lookup() gets a read only lock on the dentry, until
an unlink during which the unlinking node, will request an exclusive lock,
forcing the other nodes who care about that dentry to d_delete() it. The
effect is that we retain a very lightweight ->d_revalidate(), and at the
same time get to make large improvements to the average case performance of
the ocfs2 unlink and rename operations.This patch adds the cluster lock type which OCFS2 can attach to
dentries. A small number of fs/ocfs2/dcache.c functions are stubbed
out so that this change can compile.Signed-off-by: Mark Fasheh
-
File system lock names are very regular right now, so we really only need to
pass an extra parameter to dlmlock().Signed-off-by: Mark Fasheh
-
We just need to add a namelen field to the user_lock_res structure, and
update a few debug prints. Instead of updating all debug prints, I took the
opportunity to remove a few that are likely unnecessary these days.Signed-off-by: Mark Fasheh
-
The OCFS2 DLM uses strlen() to determine lock name length, which excludes
the possibility of putting binary values in the name string. Fix this by
requiring that string length be passed in as a parameter.Signed-off-by: Mark Fasheh
-
An AST can be delivered via the network after a lock has been removed, so no
need to print an error when we see that.Signed-off-by: Mark Fasheh
24 Sep, 2006
1 commit
-
Signed-off-by: Jeff Garzik
23 Sep, 2006
9 commits
-
Remove the EXPERIMENTAL flag from the NFS_DIRECTIO option.
Test plan:
Unset the EXPERIMENTAL kernel build option and check to see that the NFS
direct I/O option is still available.Signed-off-by: Chuck Lever
Signed-off-by: Trond Myklebust -
Comments-only change to clarify a detail of the NFS protocol and how it is
implemented in Linux.Test plan:
None.Signed-off-by: Chuck Lever
Signed-off-by: Trond Myklebust -
Signed-off-by: Josef 'Jeff' Sipek
Signed-off-by: Trond Myklebust -
RFC3530 states that the registered port 2049 for the NFS protocol should be
the default configuration in order to allow clients not to use the RPC
binding protocols.
If the mount program sends us a port=0, we therefore substitute port=2049.Signed-off-by: Trond Myklebust
-
Change the initial retry delay from 1s to 0.1s (and then back off
exponentially).Signed-off-by: Trond Myklebust
-
Retry a few times before we give up: the error is usually due to ordering
issues with asynchronous RPC calls.Signed-off-by: Trond Myklebust
-
Signed-off-by: Trond Myklebust
-
And slight optimisation of nfs_end_data_update(): directories never have
delegations anyway.Signed-off-by: Trond Myklebust
-
Currently, a read() request will return EIO even if the file has been
deleted on the server, simply because that is what the VM will return
if the call to readpage() fails to update the page.Ensure that readpage() marks the inode as stale if it receives an ESTALE.
Then return that error to userland.Signed-off-by: Trond Myklebust
