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]
Message-ID: <46F7BC3D.2040408@redhat.com>
Date:	Mon, 24 Sep 2007 09:31:41 -0400
From:	Peter Staubach <staubach@...hat.com>
To:	David Howells <dhowells@...hat.com>
CC:	viro@....linux.org.uk, hch@...radead.org,
	Trond.Myklebust@...app.com, sds@...ho.nsa.gov,
	casey@...aufler-ca.com, linux-kernel@...r.kernel.org,
	selinux@...ho.nsa.gov, linux-security-module@...r.kernel.org,
	Steve Dickson <SteveD@...hat.com>
Subject: Re: [PATCH 14/22] NFS: Use local caching

David Howells wrote:
> David Howells <dhowells@...hat.com> wrote:
>
>   
>> Peter Staubach <staubach@...hat.com> wrote:
>>
>>     
>>> Did I miss the section where the modified semantics about which
>>> mounted file systems can use the cache and which ones can not
>>> was implemented?
>>>       
>> Yes.
>>     
>
> fs/nfs/super.c:
>
> 		case Opt_sharecache:
> 			mnt->flags &= ~NFS_MOUNT_UNSHARED;
> 			break;
> 		case Opt_nosharecache:
> 			mnt->flags |= NFS_MOUNT_UNSHARED;
> 			mnt->options &= ~NFS_OPTION_FSCACHE;
> 			break;
> 		case Opt_fscache:
> 			/* sharing is mandatory with fscache */
> 			mnt->options |= NFS_OPTION_FSCACHE;
> 			mnt->flags &= ~NFS_MOUNT_UNSHARED;
> 			break;
> 		case Opt_nofscache:
> 			mnt->options &= ~NFS_OPTION_FSCACHE;
> 			break;
>
> Hmmm...  Actually, I'm not sure this is sufficient.

This doesn't seem to take into account any of the other options
which can cause sharing to be disabled.  Perhaps SteveD can add
his patch to the mix which does resolve the issues?

    Thanx...

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ