kernel.git/fs/nfs/super.c, branch linux-3.5.y

NFS: Fix a problem with the legacy binary mount code

2012-10-02T17:39:27Z

commit 872ece86ea5c367aa92f44689c2d01a1c767aeb3 upstream. Apparently, am-utils is still using the legacy binary mountdata interface, and is having trouble parsing /proc/mounts due to the 'port=' field being incorrectly set. The following patch should fix up the regression. Reported-by: Marius Tolzmann Signed-off-by: Trond Myklebust Signed-off-by: Greg Kroah-Hartman

NFS: Alias the nfs module to nfs4

2012-09-14T16:59:29Z

commit 425e776d93a7a5070b77d4f458a5bab0f924652c upstream. This allows distros to remove the line from their modprobe configuration. Signed-off-by: Bryan Schumaker Signed-off-by: Trond Myklebust [bwh: Backported to 3.2: adjust context] Signed-off-by: Ben Hutchings Signed-off-by: Greg Kroah-Hartman

NFSv4: Fix an NFSv4 mount regression

2012-07-10T17:25:39Z

The helper nfs_fs_mount() will always call nfs4_try_mount with the mount_info->fill_super argument pointing to nfs_fill_super, which is NFSv2/v3 only. Fix is to have nfs4_try_mount replace it with nfs4_fill_super. The regression was introduced by commit c40f8d1d (NFS: Create a common fs_mount() function) Signed-off-by: Trond Myklebust

NFS: Use the NFS_DEFAULT_VERSION for v2 and v3 mounts

2012-06-09T18:38:59Z

Older versions of nfs utils don't always pass a "vers=" mount option for NFS. This chould lead to attempts at using NFS v0 due to a zeroed out nfs_parsed_mount_data struct. I solve this by setting the default NFS version to NFS_DEFAULT_VERSION in the v2 and v3 cases (v4 has already been taken care of by a similar patch). Reported-by: Joerg Roedel Signed-off-by: Bryan Schumaker Signed-off-by: Trond Myklebust

NFS4: Set parsed mount data version to 4

2012-06-05T19:50:47Z

This patch only affects mounting through "-t nfs4" since it doesn't set up an nfs version to use in the mount data. The nfs client was trying to mount using NFS v0, causing either a BUG() or a protocol not supported message. Signed-off-by: Bryan Schumaker Signed-off-by: Trond Myklebust

NFS: Use proper naming conventions for nfs_client.impl_id field

2012-05-22T20:45:43Z

Clean up: When naming fields and data types, follow established conventions to facilitate accurate grep/cscope searches. Additionally, for consistency, move the impl_id field into the NFSv4- specific part of the nfs_client, and free that memory in the logic that shuts down NFSv4 nfs_clients. Introduced by commit 7d2ed9ac "NFSv4: parse and display server implementation ids," Fri Feb 17, 2012. Signed-off-by: Chuck Lever Signed-off-by: Trond Myklebust

NFS: Fix a compile issue when CONFIG_NFS_FSCACHE was undefined

2012-05-16T17:24:20Z

Reported-by: Stephen Rothwell Signed-off-by: Trond Myklebust

NFS: Pass mntfh as part of the nfs_mount_info structure

2012-05-15T00:30:31Z

This allows me to use the filehandle allocated in nfs_fs_mount() for nfs v4 mounts instead of allocating a new one. Rather than change nfs4_mount() to look almost exactly like nfs_fs_mount(), I instead remove the function. Signed-off-by: Bryan Schumaker Signed-off-by: Trond Myklebust

NFS: Allocate parsed mount data directly to the nfs_mount_info structure

2012-05-15T00:30:31Z

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

NFS: Create a single nfs_validate_mount_data() function

2012-05-15T00:30:30Z

This new function chooses between the v2/3 parser and the v4 parser by filesystem type. Signed-off-by: Bryan Schumaker Signed-off-by: Trond Myklebust