Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

NFSv4: Change the default setting of the nfs4_disable_idmapping parameter

Browse source 
Now that the use of numeric uids/gids is officially sanctioned in
RFC3530bis, it is time to change the default here to 'enabled'.

By doing so, we ensure that NFSv4 copies the behaviour of NFSv3 when we're
using the default AUTH_SYS authentication (i.e. when the client uses the
numeric uids/gids as authentication tokens), so that when new files are
created, they will appear to have the correct user/group.
It also fixes a number of backward compatibility issues when migrating
from NFSv3 to NFSv4 on a platform where the server uses different uid/gid
mappings than the client.

Note also that this setting has been successfully tested against servers
that do not support numeric uids/gids at several Connectathon/Bakeathon
events at this point, and the fall back to using string names/groups has
been shown to work well in all those test cases.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:
Trond Myklebust 2012-01-09 13:46:26 -05:00
parent 6926afd192
commit 074b1d12fe
2 changed files with 12 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Documentation/kernel-parameters.txt
View file

@ -1630,12 +1630,17 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
The default is to return 64-bit inode numbers. The default is to return 64-bit inode numbers.
nfs.nfs4_disable_idmapping= nfs.nfs4_disable_idmapping=
[NFSv4] When set, this option disables the NFSv4 [NFSv4] When set to the default of '1', this option
idmapper on the client, but only if the mount ensures that both the RPC level authentication
is using the 'sec=sys' security flavour. This may scheme and the NFS level operations agree to use
make migration from legacy NFSv2/v3 systems easier numeric uids/gids if the mount is using the
provided that the server has the appropriate support. 'sec=sys' security flavour. In effect it is
The default is to always enable NFSv4 idmapping. disabling idmapping, which can make migration from
legacy NFSv2/v3 systems to NFSv4 easier.
Servers that do not support this mode of operation
will be autodetected by the client, and it will fall
back to using the idmapper.
To turn off this behaviour, set the value to '0'.
nmi_debug= [KNL,AVR32,SH] Specify one or more actions to take nmi_debug= [KNL,AVR32,SH] Specify one or more actions to take
when a NMI is triggered. when a NMI is triggered.

2
fs/nfs/client.c
View file

@ -84,7 +84,7 @@ static int nfs_get_cb_ident_idr(struct nfs_client *clp, int minorversion)
/* /*
* Turn off NFSv4 uid/gid mapping when using AUTH_SYS * Turn off NFSv4 uid/gid mapping when using AUTH_SYS
*/ */
static int nfs4_disable_idmapping = 0; static int nfs4_disable_idmapping = 1;
/* /*
* RPC cruft for NFS * RPC cruft for NFS