kernel.git/fs/nfs/client.c, branch linux-5.16.y

NFSv4.1 query for fs_location attr on a new file system

2022-02-16T11:58:10Z

[ Upstream commit 1976b2b31462151403c9fc110204fcc2a77bdfd1 ] Query the server for other possible trunkable locations for a given file system on a 4.1+ mount. v2: -- added missing static to nfs4_discover_trunking, reported by the kernel test robot Signed-off-by: Olga Kornievskaia Signed-off-by: Anna Schumaker Signed-off-by: Sasha Levin

NFS: Fix initialisation of nfs_client cl_flags field

2022-02-16T11:58:08Z

commit 468d126dab45718feeb728319be20bd869a5eaa7 upstream. For some long forgotten reason, the nfs_client cl_flags field is initialised in nfs_get_client() instead of being initialised at allocation time. This quirk was harmless until we moved the call to nfs_create_rpc_client(). Fixes: dd99e9f98fbf ("NFSv4: Initialise connection to the server in nfs4_alloc_client()") Cc: stable@vger.kernel.org # 4.8.x Signed-off-by: Trond Myklebust Signed-off-by: Anna Schumaker Signed-off-by: Greg Kroah-Hartman

NFS: Remove the nfs4_label from the nfs4_getattr_res

2021-11-05T18:54:39Z

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

NFS: Unexport nfs_probe_fsinfo()

2021-10-20T22:09:55Z

All the callers are now in client.c so we can remove the EXPORT_SYMBOL_GPL() and make it static. Signed-off-by: Anna Schumaker Signed-off-by: Trond Myklebust

NFS: Replace calls to nfs_probe_fsinfo() with nfs_probe_server()

2021-10-20T22:09:54Z

Clean up. There are a few places where we want to probe the server, but don't actually care about the fsinfo result. Change these to use nfs_probe_server(), which handles the fattr allocation for us. Signed-off-by: Anna Schumaker Signed-off-by: Trond Myklebust

NFS: Move nfs_probe_destination() into the generic client

2021-10-20T22:09:54Z

And rename it to nfs_probe_server(). I also change it to take the nfs_fh as an argument so callers can choose what filehandle to probe. Signed-off-by: Anna Schumaker Signed-off-by: Trond Myklebust

SUNRPC enforce creation of no more than max_connect xprts

2021-08-27T20:37:29Z

If we are adding new transports via rpc_clnt_test_and_add_xprt() then check if we've reached the limit. Currently only pnfs path adds transports via that function but this is done in preparation when the client would add new transports when session trunking is detected. A warning is logged if the limit is reached. Signed-off-by: Olga Kornievskaia Signed-off-by: Anna Schumaker

NFSv4 introduce max_connect mount options

2021-08-27T20:37:17Z

This option will control up to how many xprts can the client establish to the server with a distinct address (that means nconnect connections are not counted towards this new limit). This patch is setting up nfs structures to keeep track of the max_connect limit (does not enforce it). The default value is kept at 1 so that no current mounts that don't want any additional connections would be effected. The maximum value is set at 16. Mounts to DS are not limited to default value of 1 but instead set to the maximum default value of 16 (NFS_MAX_TRANSPORTS). Signed-off-by: Olga Kornievskaia Signed-off-by: Anna Schumaker

NFS: Fix a potential NULL dereference in nfs_get_client()

2021-06-03T14:14:42Z

None of the callers are expecting NULL returns from nfs_get_client() so this code will lead to an Oops. It's better to return an error pointer. I expect that this is dead code so hopefully no one is affected. Fixes: 31434f496abb ("nfs: check hostname in nfs_get_client") Signed-off-by: Dan Carpenter Signed-off-by: Trond Myklebust

NFS: Split attribute support out from the server capabilities

2021-04-14T13:36:29Z

There are lots of attributes, and they are crowding out the bit space. Signed-off-by: Trond Myklebust