linux-toradex.git/fs/nfsd/nfs3proc.c, branch v4.4.72

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells 
Signed-off-by: Al Viro

nfsd: allow turning off nfsv3 readdir_plus

2014-08-18T19:12:14+00:00

One of our customer's application only needs file names, not file
attributes. With directories having 10K+ inodes (assuming buffer cache
has directory blocks cached having file names, but inode cache is
limited and hence need eviction of older cached inodes), older inodes
are evicted periodically. So if they keep on doing readdir(2) from NSF
client on multiple directories, some directory's files are periodically
removed from inode cache and hence new readdir(2) on same directory
requires disk access to bring back inodes again to inode cache.

As READDIRPLUS request fetches attributes also, doing getattr on each
file on server, it causes unnecessary disk accesses. If READDIRPLUS on
NFS client is returned with -ENOTSUPP, NFS client uses READDIR request
which just gets the names of the files in a directory, not attributes,
hence avoiding disk accesses on server.

There's already a corresponding client-side mount option, but an export
option reduces the need for configuration across multiple clients.

This flag affects NFSv3 only.  If it turns out it's needed for NFSv4 as
well then we may have to figure out how to extend the behavior to NFSv4,
but it's not currently obvious how to do that.

Signed-off-by: Rajesh Ghanekar 
Signed-off-by: J. Bruce Fields

nfsd3: Check write permission after checking existence

2014-08-17T16:00:14+00:00

When creating a file that already exists in a read-only directory with
O_EXCL, the NFSv3 server returns EACCES rather than EEXIST (which local
files and the NFSv4 server return).  Fix this by checking the MAY_CREATE
permission only if the file does not exist.  Since this already happens
in do_nfsd_create, the check in nfsd3_proc_create can simply be removed.

Signed-off-by: Ross Lagerwall 
Signed-off-by: J. Bruce Fields

NFSD: Remove iattr parameter from nfsd_symlink()

2014-07-08T21:14:31+00:00

Commit db2e747b1499 (vfs: remove mode parameter from vfs_symlink())
have remove mode parameter from vfs_symlink.
So that, iattr isn't needed by nfsd_symlink now, just remove it.

Signed-off-by: Kinglong Mee 
Signed-off-by: J. Bruce Fields

nfsd: let nfsd_symlink assume null-terminated data

2014-07-08T21:14:23+00:00

Currently nfsd_symlink has a weird hack to serve callers who don't
null-terminate symlink data: it looks ahead at the next byte to see if
it's zero, and copies it to a new buffer to null-terminate if not.

That means callers don't have to null-terminate, but they *do* have to
ensure that the byte following the end of the data is theirs to read.

That's a bit subtle, and the NFSv4 code actually got this wrong.

So let's just throw out that code and let callers pass null-terminated
strings; we've already fixed them to do that.

Signed-off-by: J. Bruce Fields

NFSD: Using min/max/min_t/max_t for calculate

2014-06-23T15:31:36+00:00

Signed-off-by: Kinglong Mee 
Signed-off-by: J. Bruce Fields

switch vfs_getattr() to struct path

2013-02-26T07:46:08+00:00

Signed-off-by: Al Viro

nfsd4: cleanup: replace rq_resused count by rq_next_page pointer

2012-12-18T03:00:16+00:00

It may be a matter of personal taste, but I find this makes the code
clearer.

Signed-off-by: J. Bruce Fields

nfsd: do_nfsd_create verf argument is a u32

2012-08-20T22:39:49+00:00

The types here are actually a bit of a mess.  For now cast as we do in
the v4 case.

Signed-off-by: J. Bruce Fields

nfsd41: make sure nfs server process OPEN with EXCLUSIVE4_1 correctly

2011-04-30T00:47:52+00:00

The NFS server uses nfsd_create_v3 to handle EXCLUSIVE4_1 opens, but
that function is not prepared to handle them.

Rename nfsd_create_v3() to do_nfsd_create(), and add handling of
EXCLUSIVE4_1.

Signed-off-by: Mi Jinlong 
Signed-off-by: J. Bruce Fields