linux-kernel - Re: [PATCH][RFC] NFS: Propagate 'fsc' mount option through automounts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 09 Jul 2009 13:50:51 -0400
From:	Trond Myklebust <Trond.Myklebust@...app.com>
To:	David Howells <dhowells@...hat.com>
Cc:	steved@...hat.com, nfsv4@...ux-nfs.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH][RFC] NFS: Propagate 'fsc' mount option through
 automounts

On Thu, 2009-07-09 at 18:27 +0100, David Howells wrote:
> Propagate the NFS 'fsc' mount option through NFS automounts of various types.
> 
> This is now required as commit:
> 
> 	commit c02d7adf8c5429727a98bad1d039bccad4c61c50
> 	Author: Trond Myklebust <Trond.Myklebust@...app.com>
> 	Date:   Mon Jun 22 15:09:14 2009 -0400
> 
> 	NFSv4: Replace nfs4_path_walk() with VFS path lookup in a private namespace
> 
> now uses VFS-driven automounting to reach all submounts barring the root, thus
> preventing fscaching from being enabled on any submount other than the root.
> 
> This patch gets around that by propagating the NFS_OPTION_FSCACHE flag across
> automounts.
> 
> Note, however, that it doesn't propagate the uniquifier in the case of
> 'fsc=<xxx>' being passed to mount.  This is probably wrong, and needs looking
> at.

Why not just use the mount path as the default uniquifier?

> Signed-off-by: David Howells <dhowells@...hat.com>
> ---
> 
>  fs/nfs/client.c |    1 +
>  fs/nfs/super.c  |    6 ++++++
>  2 files changed, 7 insertions(+), 0 deletions(-)
> 
> 
> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> index c2d0616..0949b46 100644
> --- a/fs/nfs/client.c
> +++ b/fs/nfs/client.c
> @@ -964,6 +964,7 @@ static void nfs_server_copy_userdata(struct nfs_server *target, struct nfs_serve
>  	target->acdirmin = source->acdirmin;
>  	target->acdirmax = source->acdirmax;
>  	target->caps = source->caps;
> +	target->options = source->options;

BTW: Why does fscache require a private flag field?

>  }
>  
>  /*
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 0b4cbdc..bfab16f 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -2214,6 +2214,7 @@ static int nfs_xdev_get_sb(struct file_system_type *fs_type, int flags,
>  	struct nfs_server *server;
>  	struct dentry *mntroot;
>  	int (*compare_super)(struct super_block *, void *) = nfs_compare_super;
> +	struct nfs_parsed_mount_data parsed_data = { .fscache_uniq = NULL, };

Rather than wasting all this space on the stack, how about just changing
the second argument of nfs_fscache_get_super_cookie()? You only use the
pointer to data->fscache_uniq.

>  	struct nfs_sb_mountdata sb_mntdata = {
>  		.mntflags = flags,
>  	};

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@...app.com
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/