nfs-utils.git/support/include/nfs, branch fixrootccache

nfsd: don't enable a UDP socket by default

2017-04-05T17:28:11+00:00

Most major NFS clients have supported TCP for at least a decade now,
and v4-only shops are becoming more prevalent. It seems reasonable that
serving over UDP should be something that is "opt-in".

I've always hesitated to do this in the past, but now that we have
nfs.conf, it seems like the time may be right to disable UDP in default
configurations. In particular, it would be good to try this in the more
bleeding edge distros (Fedora, Ubuntu, SuSE, etc...) and see how
problematic it is.

Change the default in rpc.nfsd to just open TCP ports by default. Add
new -u and -t options that allow users to explicitly override what's
in the config file, and update the usage message and manpage.

Signed-off-by: Jeff Layton 
Signed-off-by: Steve Dickson

nfsd: Allow the caller to turn off NFSv4.0 without turning off NFSv4.x

2017-04-05T17:27:57+00:00

The new semantic is that '-N4' turns off all NFSv4 minor versions, while
'-V4' turns them all on. In order to turn off just minor version x (x >= 0),
use -N4.x, and to turn it back on. '-V4.x'.

Note that on older kernels, attempting to use -N4.0 and -V4.0 is
equivalent to specifying -N4 or -V4.

Signed-off-by: Trond Myklebust 
Signed-off-by: Steve Dickson

exportfs: support "security_label" export option

2017-01-12T15:16:42+00:00

On recent kernels only exports with NFSEXP_SECURITY_LABEL set will
export security labels.

Signed-off-by: J. Bruce Fields 
Signed-off-by: Steve Dickson

Remove all use of the nfsctl system call.

2016-12-06T16:15:37+00:00

This systemcall was deprecated early in the 2.6 series
as it was replaced by an in-kernel cache which was refilled
using an upcall.  All communication to kernel is now through
the nfsd filesystem.

The nfsctl systemcall itself was removed in 3.1.

It is unlikely to have been used for over a decade.

To remove all uses for the nfsctl systemcall, and call code that only
runs when "new_cache" is false.  We now assume "new_cache" is always
true.

This allows the removal of several files as well as assorted functions.

Signed-off-by: NeilBrown 
Signed-off-by: Steve Dickson

nfs-utils: add support for the "pnfs" export option

2015-04-02T15:57:36+00:00

This goes along with the patch just sent to Bruce to make pnfs
support conditional.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Steve Dickson

nfs-utils: Allow turning off nfsv3 readdir_plus

2014-08-20T18:00:59+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: Steve Dickson

nfsd: support NFS4_MAXMINOR up to the number an unsigned int can keep

2014-02-13T17:44:06+00:00

This implementation allows specifying NFS4 minor version numbers up
to the number of bits available in int data type (typically 32 on
Linux)

This is based on an idea mentioned by
J. Bruce Fields  mentioned on the linux-nfs mailing list.

I changed the data type back from an array to two bit fields, one for
storing whether the minor version was specified on the command line
and the second one for storing whether it was set or unset.  This
change was done to prevent blowing up the allocated stack space in an
unnecessary fashion.

Acked-by: J. Bruce Fields 
Signed-off-by: Robert Schiele 
Signed-off-by: Steve Dickson

nfsd: fix minorversion-choosing interface

2014-01-07T20:57:48+00:00

From: "J. Bruce Fields" 

By unconditionally adding ?4.2 to the version string written to the
kernel we make nfs-utils incompatible with pre-4.2-supporting kernels.

Ditto for 4.1.  This problem was introduced by
12a590f8d556c00a9502eeebaa763d906222d521 "rpc.nfsd: Allow v4.2 server
support with the -V option", which also change nfsd to unconditionally
pass ?4.2.

Instead, just don't mention 4.1 or 4.2 unless the commandline has
specifically requested that one or the other be turned on or off.

Tested-by: Joakim Tjernlund 
Reported-by: Joakim Tjernlund 
Signed-off-by: J. Bruce Fields 
Signed-off-by: Steve Dickson

rpc.nfsd: Allow v4.2 server support with the -V option

2013-08-19T17:04:50+00:00

Signed-off-by: Steve Dickson

rpc.nfsd: No longer advertise NFS v2 support.

2013-08-19T17:04:49+00:00

Changed the default protocol versions that rpc.nfsd
register with rpcbind to just 3 and 4. Version 2
can still be enabled with the '-V' flag, but it
will not be on by default.

Signed-off-by: Steve Dickson