linux-toradex.git/include/linux/nfs_fs.h, branch imx-android-r13.2

nfs: when attempting to open a directory, fall back on normal lookup (try #5)

2011-11-26T17:09:59+00:00

commit 1788ea6e3b2a58cf4fb00206e362d9caff8d86a7 upstream.

commit d953126 changed how nfs_atomic_lookup handles an -EISDIR return
from an OPEN call. Prior to that patch, that caused the client to fall
back to doing a normal lookup. When that patch went in, the code began
returning that error to userspace. The d_revalidate codepath however
never had the corresponding change, so it was still possible to end up
with a NULL ctx->state pointer after that.

That patch caused a regression. When we attempt to open a directory that
does not have a cached dentry, that open now errors out with EISDIR. If
you attempt the same open with a cached dentry, it will succeed.

Fix this by reverting the change in nfs_atomic_lookup and allowing
attempts to open directories to fall back to a normal lookup

Also, add a NFSv4-specific f_ops->open routine that just returns
-ENOTDIR. This should never be called if things are working properly,
but if it ever is, then the dprintk may help in debugging.

To facilitate this, a new file_operations field is also added to the
nfs_rpc_ops struct.

Signed-off-by: Jeff Layton 
Signed-off-by: Trond Myklebust 
Signed-off-by: Greg Kroah-Hartman

NFS: Fix spurious readdir cookie loop messages

2011-08-05T04:58:40+00:00

commit 0c0308066ca53fdf1423895f3a42838b67b3a5a8 upstream.

If the directory contents change, then we have to accept that the
file->f_pos value may shrink if we do a 'search-by-cookie'. In that
case, we should turn off the loop detection and let the NFS client
try to recover.

The patch also fixes a second loop detection bug by ensuring
that after turning on the ctx->duped flag, we read at least one new
cookie into ctx->dir_cookie before attempting to match with
ctx->dup_cookie.

Reported-by: Petr Vandrovec 
Signed-off-by: Trond Myklebust 
Signed-off-by: Greg Kroah-Hartman

NFSv4.1: layoutcommit

2011-03-23T19:29:04+00:00

The filelayout driver sends LAYOUTCOMMIT only when COMMIT goes to
the data server (as opposed to the MDS) and the data server WRITE
is not NFS_FILE_SYNC.

Only whole file layout support means that there is only one IOMODE_RW layout
segment.

Signed-off-by: Andy Adamson 
Signed-off-by: Alexandros Batsakis 
Signed-off-by: Boaz Harrosh 
Signed-off-by: Dean Hildebrand 
Signed-off-by: Fred Isaman 
Signed-off-by: Mingyang Guo 
Signed-off-by: Tao Guo 
Signed-off-by: Zhang Jingwang 
Tested-by: Boaz Harrosh 
Signed-off-by: Benny Halevy 
Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

NFSv4.1: filelayout driver specific code for COMMIT

2011-03-23T19:29:04+00:00

Implement all the hooks created in the previous patches.
This requires exporting quite a few functions and adding a few
structure fields.

Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

NFSv4.1: add generic layer hooks for pnfs COMMIT

2011-03-23T19:29:03+00:00

We create three major hooks for the pnfs code.

pnfs_mark_request_commit() is called during writeback_done from
nfs_mark_request_commit, which gives the driver an opportunity to
claim it wants control over commiting a particular req.

pnfs_choose_commit_list() is called from nfs_scan_list
to choose which list a given req should be added to, based on
where we intend to send it for COMMIT.  It is up to the driver
to have preallocated list headers for each destination it may need.

pnfs_commit_list() is how the driver actually takes control, it is
used instead of nfs_commit_list().

In order to pass information between the above functions, we create
a union in nfs_page to hold a lseg (which is possible because the req is
not on any list while in transition), and add some flags to indicate
if we need to use the pnfs code.

Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

NFS: Detect loops in a readdir due to bad cookies

2011-03-23T19:14:27+00:00

Some filesystems (such as ext4) can return the same cookie value for
multiple files.  If we try to start a readdir with one of these cookies,
the server will return the first file found with a cookie of the same
value.  This can cause the client to enter an infinite loop.

Signed-off-by: Bryan Schumaker 
Signed-off-by: Trond Myklebust

NFS: Create nfs_open_dir_context

2011-03-23T19:13:11+00:00

nfs_opendir() created a context that held much more information than we
need for a readdir.  This patch introduces a slimmed-down
nfs_open_dir_context that contains only the cookie and the cred used for
RPC operations.  The new context will eventually be used to help detect
readdir loops.

Signed-off-by: Bryan Schumaker 
Signed-off-by: Trond Myklebust

FS: Use stable writes when not doing a bulk flush

2011-03-22T01:08:17+00:00

If we're only doing a single write, and there are no other unstable
writes being queued up, we might want to just flip to using a stable
write RPC call.

Reviewed-by: NeilBrown 
Signed-off-by: Trond Myklebust

NFS: change nfs_writeback_done to return void

2011-03-11T20:38:40+00:00

The return values are not used by any callers.

Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

NFS: Use d_automount() rather than abusing follow_link()

2011-01-16T01:07:34+00:00

Make NFS use the new d_automount() dentry operation rather than abusing
follow_link() on directories.

Signed-off-by: David Howells 
Acked-by: Trond Myklebust 
Acked-by: Ian Kent 
Signed-off-by: Al Viro