Currently the kernel returns -EINVAL, which makes it hard to distinguish this situation from the case where an invalid mount option was specified. Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> --- fs/nfs/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/nfs/super.c b/fs/nfs/super.c index 3f5a7a8..cebdb26 100644 --- a/fs/nfs/super.c +++ b/fs/nfs/super.c @@ -2156,7 +2156,7 @@ nfs_compare_remount_data(struct nfs_server *nfss, data->nfs_server.addrlen != nfss->nfs_client->cl_addrlen || !rpc_cmp_addr((struct sockaddr *)&data->nfs_server.address, (struct sockaddr *)&nfss->nfs_client->cl_addr)) - return -EINVAL; + return -EBUSY; return 0; } -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
