From: Eric Paris <eparis@redhat.com>
To: Dave Quigley <dpquigl@tycho.nsa.gov>
Cc: linux-nfs@vger.kernel.org, selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, steved@redhat.com,
jlayton@redhat.com, sds@tycho.nsa.gov, jmorris@namei.org,
casey@schaufler-ca.com, trond.myklebust@fys.uio.no,
chuck.lever@oracle.com, hch@infradead.org
Subject: Re: [PATCH -v2] NFS/LSM: allow NFS to control all of its own mount options
Date: Mon, 03 Mar 2008 15:10:55 -0500 [thread overview]
Message-ID: <1204575055.3216.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1204573122.14520.90.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
On Mon, 2008-03-03 at 14:38 -0500, Dave Quigley wrote:
> > This patch was tested with NFSv3 mounts and solves all of the
> > regressions that have been introduced in the NFS code. It supports both
> > the binary interface and text options without pushing LSM specific
> > parsing into the FS. It doesn't introduce the new LSM constructs
> > necessary to show these mount options in /proc/mounts suggested by
> > Miklos Szeredi but that will be coming in 2.6.26 (it's not a regression
> > or bug fix). I also do not have the proper security_sb_set_mnt_opts()
> > call in nfs4_get_sb due to a lack of a testing environment, but will add
> > that in 2.6.26 as well.
>
> I see above that the patch does not provide this support for NFSv4. Do
> you intend on adding this in the future or is it being deferred to
> someone else?
I believe it is just the very same addition to nfs4_get_sb() that i did
in nfs_get_sb and plan to test and do that myself in the next release.
I'm just trying to make this patch as absolutely small as possible while
still fixing all the problems to get it into 2.6.25.
-Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Paris <eparis@redhat.com>
To: Dave Quigley <dpquigl@tycho.nsa.gov>
Cc: linux-nfs@vger.kernel.org, selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, steved@redhat.com,
jlayton@redhat.com, sds@tycho.nsa.gov, jmorris@namei.org,
casey@schaufler-ca.com, trond.myklebust@fys.uio.no,
chuck.lever@oracle.com, hch@infradead.org
Subject: Re: [PATCH -v2] NFS/LSM: allow NFS to control all of its own mount options
Date: Mon, 03 Mar 2008 15:10:55 -0500 [thread overview]
Message-ID: <1204575055.3216.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1204573122.14520.90.camel@moss-terrapins.epoch.ncsc.mil>
On Mon, 2008-03-03 at 14:38 -0500, Dave Quigley wrote:
> > This patch was tested with NFSv3 mounts and solves all of the
> > regressions that have been introduced in the NFS code. It supports both
> > the binary interface and text options without pushing LSM specific
> > parsing into the FS. It doesn't introduce the new LSM constructs
> > necessary to show these mount options in /proc/mounts suggested by
> > Miklos Szeredi but that will be coming in 2.6.26 (it's not a regression
> > or bug fix). I also do not have the proper security_sb_set_mnt_opts()
> > call in nfs4_get_sb due to a lack of a testing environment, but will add
> > that in 2.6.26 as well.
>
> I see above that the patch does not provide this support for NFSv4. Do
> you intend on adding this in the future or is it being deferred to
> someone else?
I believe it is just the very same addition to nfs4_get_sb() that i did
in nfs_get_sb and plan to test and do that myself in the next release.
I'm just trying to make this patch as absolutely small as possible while
still fixing all the problems to get it into 2.6.25.
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: Eric Paris <eparis-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dave Quigley <dpquigl-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
selinux <selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>,
linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
steved-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org,
jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org,
casey-iSGtlc1asvQWG2LlvL+J4A@public.gmane.org,
trond.myklebust-41N18TsMXrtuMpJDpNschA@public.gmane.org,
chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH -v2] NFS/LSM: allow NFS to control all of its own mount options
Date: Mon, 03 Mar 2008 15:10:55 -0500 [thread overview]
Message-ID: <1204575055.3216.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1204573122.14520.90.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
On Mon, 2008-03-03 at 14:38 -0500, Dave Quigley wrote:
> > This patch was tested with NFSv3 mounts and solves all of the
> > regressions that have been introduced in the NFS code. It supports both
> > the binary interface and text options without pushing LSM specific
> > parsing into the FS. It doesn't introduce the new LSM constructs
> > necessary to show these mount options in /proc/mounts suggested by
> > Miklos Szeredi but that will be coming in 2.6.26 (it's not a regression
> > or bug fix). I also do not have the proper security_sb_set_mnt_opts()
> > call in nfs4_get_sb due to a lack of a testing environment, but will add
> > that in 2.6.26 as well.
>
> I see above that the patch does not provide this support for NFSv4. Do
> you intend on adding this in the future or is it being deferred to
> someone else?
I believe it is just the very same addition to nfs4_get_sb() that i did
in nfs_get_sb and plan to test and do that myself in the next release.
I'm just trying to make this patch as absolutely small as possible while
still fixing all the problems to get it into 2.6.25.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-03 20:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 19:42 [PATCH -v2] NFS/LSM: allow NFS to control all of its own mount options Eric Paris
2008-03-03 19:42 ` Eric Paris
2008-03-03 19:38 ` Dave Quigley
2008-03-03 19:38 ` Dave Quigley
[not found] ` <1204573122.14520.90.camel-88+Bj4OksMGWPftkNcioYDMZycKHmlmlfvIqQ387n9k@public.gmane.org>
2008-03-03 20:10 ` Eric Paris [this message]
2008-03-03 20:10 ` Eric Paris
2008-03-03 20:10 ` Eric Paris
2008-03-03 19:51 ` Dave Quigley
2008-03-03 19:51 ` Dave Quigley
2008-03-04 22:54 ` James Morris
2008-03-04 22:54 ` James Morris
2008-03-05 13:48 ` Jeff Layton
2008-03-05 14:11 ` Eric Paris
2008-03-05 14:11 ` Eric Paris
[not found] ` <1204726270.3216.196.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-03-05 14:27 ` Jeff Layton
2008-03-05 14:27 ` Jeff Layton
[not found] ` <20080305092758.1bfe9687-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:34 ` Eric Paris
2008-03-05 14:42 ` How to handle NFS and conflicting " Eric Paris
2008-03-05 14:46 ` Stephen Smalley
2008-03-05 14:54 ` Eric Paris
2008-03-05 17:15 ` Casey Schaufler
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=1204575055.3216.49.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=chuck.lever@oracle.com \
--cc=dpquigl@tycho.nsa.gov \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=steved@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.