From: Dave Hansen <haveblue@us.ibm.com>
To: Miklos Szeredi <miklos@szeredi.hu>
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
Subject: Re: r-o bind in nfsd
Date: Fri, 21 Mar 2008 14:08:01 -0700 [thread overview]
Message-ID: <1206133681.30471.37.camel@nimitz.home.sr71.net> (raw)
In-Reply-To: <E1JcmLz-0001n1-RC@pomaz-ex.szeredi.hu>
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
next prev parent reply other threads:[~2008-03-21 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 14:59 r-o bind in nfsd Miklos Szeredi
2008-03-21 15:54 ` Al Viro
2008-03-21 16:24 ` Miklos Szeredi
2008-03-21 16:35 ` Al Viro
2008-03-21 16:54 ` Miklos Szeredi
2008-03-21 17:08 ` Miklos Szeredi
2008-03-21 18:11 ` Al Viro
2008-03-21 18:52 ` Miklos Szeredi
2008-03-21 19:49 ` Al Viro
2008-03-21 20:23 ` Miklos Szeredi
2008-03-22 2:20 ` Tetsuo Handa
2008-03-21 21:08 ` Dave Hansen [this message]
2008-03-21 21:17 ` Miklos Szeredi
2008-03-25 2:52 ` Neil Brown
2008-03-25 11:45 ` Tetsuo Handa
2008-03-25 22:32 ` NeilBrown
[not found] ` <20080325224919.GM10722@ZenIV.linux.org.uk>
2008-03-25 23:29 ` NeilBrown
2008-03-26 12:04 ` Stephen Smalley
2008-03-26 16:47 ` Serge E. Hallyn
2008-03-26 21:35 ` James Morris
2008-03-27 0:29 ` Serge E. Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1206133681.30471.37.camel@nimitz.home.sr71.net \
--to=haveblue@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=neilb@suse.de \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).