From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: r-o bind in nfsd Date: Fri, 21 Mar 2008 14:08:01 -0700 Message-ID: <1206133681.30471.37.camel@nimitz.home.sr71.net> References: <20080321155451.GU10722@ZenIV.linux.org.uk> <20080321163520.GV10722@ZenIV.linux.org.uk> <20080321181105.GW10722@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, neilb@suse.de, akpm@linux-foundation.org, hch@infradead.org, linux-security-module@vger.kernel.org, jmorris@namei.org To: Miklos Szeredi Return-path: Received: from e32.co.us.ibm.com ([32.97.110.150]:57787 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753773AbYCUVIK (ORCPT ); Fri, 21 Mar 2008 17:08:10 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, 2008-03-21 at 19:52 +0100, Miklos Szeredi wrote: > Traditionally we have syscalls, and nfsd. Both of them want the > security checks, and I think nfsd wants the read-only mount checking > as well, but I'm not entirely sure. Maybe we can handle that by just > making nfsd acquire a write-ref on the mount and keep it while it's > exported. The only question for me would be where the current r/o checks are happening (IS_RDONLY()). I generally based my patches on replacing those calls. -- Dave