From: Chuck Lever <chucklever@gmail.com>
To: Trond Myklebust <trondmy@gmail.com>
Cc: Steve Dickson <SteveD@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [RFC PATCH v2 0/7] Add a root_dir option to nfs.conf
Date: Tue, 21 May 2019 13:40:04 -0400 [thread overview]
Message-ID: <708D03B6-AEE1-42D6-ABDF-FB1AA5FC9A94@gmail.com> (raw)
In-Reply-To: <20190521124701.61849-1-trond.myklebust@hammerspace.com>
Hi Trond -
> On May 21, 2019, at 8:46 AM, Trond Myklebust <trondmy@gmail.com> wrote:
>
> The following patchset adds support for the 'root_dir' configuration
> option for nfsd in nfs.conf. If a user sets this option to a valid
> directory path, then nfsd will act as if it is confined to a chroot
> jail based on that directory. All paths in /etc/exporfs and from
> exportfs are then resolved relative to that directory.
What about files under /proc that mountd might access? I assume these
pathnames are not affected.
Aren't there also one or two other files that maintain export state
like /var/lib/nfs/rmtab? Are those affected?
IMHO it could be less confusing to administrators to make root_dir an
[exportfs] option instead of a [mountd] option, if this is not a true
chroot of mountd.
> Trond Myklebust (7):
> mountd: Ensure we don't share cache file descriptors among processes.
> Add a simple workqueue mechanism
> Add utilities for resolving nfsd paths and stat()ing them
> Add a helper to return the real path given an export entry
> Add helpers to read/write to a file through the chrooted thread
> Add support for the nfsd rootdir configuration option to rpc.mountd
> Add support for the nfsd root directory to exportfs
>
> aclocal/libpthread.m4 | 13 +-
> configure.ac | 6 +-
> nfs.conf | 1 +
> support/export/export.c | 24 +++
> support/include/Makefile.am | 2 +
> support/include/exportfs.h | 1 +
> support/include/nfsd_path.h | 17 ++
> support/include/nfslib.h | 1 +
> support/include/workqueue.h | 22 +++
> support/misc/Makefile.am | 3 +-
> support/misc/mountpoint.c | 5 +-
> support/misc/nfsd_path.c | 175 +++++++++++++++++++++
> support/misc/workqueue.c | 306 ++++++++++++++++++++++++++++++++++++
> support/nfs/exports.c | 4 +
> systemd/nfs.conf.man | 3 +-
> utils/exportfs/Makefile.am | 2 +-
> utils/exportfs/exportfs.c | 32 +++-
> utils/mountd/Makefile.am | 3 +-
> utils/mountd/cache.c | 79 +++++++---
> utils/mountd/mountd.c | 13 +-
> utils/nfsd/nfsd.man | 6 +
> 21 files changed, 676 insertions(+), 42 deletions(-)
> create mode 100644 support/include/nfsd_path.h
> create mode 100644 support/include/workqueue.h
> create mode 100644 support/misc/nfsd_path.c
> create mode 100644 support/misc/workqueue.c
>
> --
> 2.21.0
>
--
Chuck Lever
chucklever@gmail.com
next prev parent reply other threads:[~2019-05-21 17:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 12:46 [RFC PATCH v2 0/7] Add a root_dir option to nfs.conf Trond Myklebust
2019-05-21 12:46 ` [RFC PATCH v2 1/7] mountd: Ensure we don't share cache file descriptors among processes Trond Myklebust
2019-05-21 12:46 ` [RFC PATCH v2 2/7] Add a simple workqueue mechanism Trond Myklebust
2019-05-21 12:46 ` [RFC PATCH v2 3/7] Add utilities for resolving nfsd paths and stat()ing them Trond Myklebust
2019-05-21 12:46 ` [RFC PATCH v2 4/7] Add a helper to return the real path given an export entry Trond Myklebust
2019-05-21 12:46 ` [RFC PATCH v2 5/7] Add helpers to read/write to a file through the chrooted thread Trond Myklebust
2019-05-21 12:47 ` [RFC PATCH v2 6/7] Add support for the nfsd rootdir configuration option to rpc.mountd Trond Myklebust
2019-05-21 12:47 ` [RFC PATCH v2 7/7] Add support for the nfsd root directory to exportfs Trond Myklebust
2019-05-21 17:40 ` Chuck Lever [this message]
2019-05-21 18:17 ` [RFC PATCH v2 0/7] Add a root_dir option to nfs.conf Trond Myklebust
2019-05-21 18:59 ` Trond Myklebust
2019-05-21 19:06 ` Chuck Lever
2019-05-21 19:58 ` Trond Myklebust
2019-05-28 15:25 ` Steve Dickson
2019-05-28 16:44 ` Trond Myklebust
2019-05-28 16:47 ` Chuck Lever
2019-05-28 16:50 ` Trond Myklebust
2019-05-28 17:40 ` Steve Dickson
2019-05-28 18:19 ` Trond Myklebust
2019-05-28 19:33 ` Steve Dickson
2019-05-28 15:30 ` Chuck Lever
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=708D03B6-AEE1-42D6-ABDF-FB1AA5FC9A94@gmail.com \
--to=chucklever@gmail.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@gmail.com \
/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