linux-kernel - Re: [PATCH 24/27] NFS: Use local caching [try #2]

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] [day] [month] [year] [list]

Date:	Thu, 07 Feb 2008 10:57:49 +0000
From:	David Howells <dhowells@...hat.com>
To:	chuck.lever@...cle.com
Cc:	dhowells@...hat.com, Trond.Myklebust@...app.com,
	nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org, selinux@...ho.nsa.gov,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 24/27] NFS: Use local caching [try #2]

Chuck Lever <chuck.lever@...cle.com> wrote:

> > @@ -95,12 +100,25 @@ struct nfs_server {
> >  	unsigned int		acdirmin;
> >  	unsigned int		acdirmax;
> >  	unsigned int		namelen;
> > +	unsigned int		options;	/* extra options enabled by mount */
> > +#define NFS_OPTION_FSCACHE	0x00000001	/* - local caching enabled */
> 
> Why did you choose to create a new field for this rather than setting up a new
> NFS_MNT flag?  The new in-kernel NFS mount option parser uses the NFS_MNT
> flags too.

There aren't any NFS_MNT flags, so I presume you mean NFS_MOUNT flags.  As I
understood Trond, it's not permitted to add new such flags except in really
special circumstances as these are part of the mount syscall interface.  I
took this to mean that I should record the option elsewhere than in
server->flags.

David
--
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/