From: Trond Myklebust <trondmy@gmail.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [RFC PATCH 0/5] Add a chroot option to nfs.conf
Date: Tue, 14 May 2019 16:41:48 -0400 [thread overview]
Message-ID: <20190514204153.79603-1-trond.myklebust@hammerspace.com> (raw)
The following patchset aims to allow the configuration of a 'chroot
jail' to rpc.nfsd, and allowing us to export a filesystem /foo (and
possibly subtrees) as '/'.
Trond Myklebust (5):
mountd: Ensure we don't share cache file descriptors among processes.
Add a simple workqueue mechanism
Add a helper to write to a file through the chrooted thread
Add support for chrooted exports
Add support for chroot in exportfs
aclocal/libpthread.m4 | 13 +-
configure.ac | 6 +-
nfs.conf | 1 +
support/include/misc.h | 11 ++
support/misc/Makefile.am | 2 +-
support/misc/workqueue.c | 267 +++++++++++++++++++++++++++++++++++++
systemd/nfs.conf.man | 3 +-
utils/exportfs/Makefile.am | 2 +-
utils/exportfs/exportfs.c | 31 ++++-
utils/mountd/Makefile.am | 3 +-
utils/mountd/cache.c | 39 +++++-
utils/mountd/mountd.c | 5 +-
utils/nfsd/nfsd.man | 4 +
13 files changed, 369 insertions(+), 18 deletions(-)
create mode 100644 support/misc/workqueue.c
--
2.21.0
next reply other threads:[~2019-05-14 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 20:41 Trond Myklebust [this message]
2019-05-14 20:41 ` [RFC PATCH 1/5] mountd: Ensure we don't share cache file descriptors among processes Trond Myklebust
2019-05-14 20:41 ` [RFC PATCH 2/5] Add a simple workqueue mechanism Trond Myklebust
2019-05-14 20:41 ` [RFC PATCH 3/5] Add a helper to write to a file through the chrooted thread Trond Myklebust
2019-05-14 20:41 ` [RFC PATCH 4/5] Add support for chrooted exports Trond Myklebust
2019-05-14 20:41 ` [RFC PATCH 5/5] Add support for chroot in exportfs Trond Myklebust
2019-05-15 14:14 ` [RFC PATCH 4/5] Add support for chrooted exports J. Bruce Fields
2019-05-15 14:01 ` [RFC PATCH 0/5] Add a chroot option to nfs.conf J. Bruce Fields
2019-05-15 14:38 ` Trond Myklebust
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=20190514204153.79603-1-trond.myklebust@hammerspace.com \
--to=trondmy@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).