From: Doug Nazar <nazard@nazar.ca>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] nfs-utils patches
Date: Wed, 22 Jul 2020 01:53:50 -0400 [thread overview]
Message-ID: <20200722055354.28132-1-nazard@nazar.ca> (raw)
A few more as I progress through all the utils. There isn't any
dependency on the previous patches.
Although idmapd client support is depreciated, the kernel still falls
back to using it if the upcall fails.
Wasn't originally going to send the last patch upstream, but figured
might as well, and let you decide if it's wanted. Basically allows you
to load the plugins from a development source tree for testing instead
of requiring them to be installed in their final location.
Thanks,
Doug
Doug Nazar (4):
exportfs: Fix a few valgrind warnings
idmapd: Add graceful exit and resource cleanup
idmapd: Fix client mode support
nfsidmap: Allow overriding location of method libraries
support/nfs/exports.c | 1 +
support/nfsidmap/libnfsidmap.c | 40 +++++--
utils/exportfs/exportfs.c | 7 +-
utils/idmapd/idmapd.c | 211 +++++++++++++++++++++++----------
4 files changed, 183 insertions(+), 76 deletions(-)
--
2.26.2
next reply other threads:[~2020-07-22 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 5:53 Doug Nazar [this message]
2020-07-22 5:53 ` [PATCH 1/4] exportfs: Fix a few valgrind warnings Doug Nazar
2020-07-22 5:53 ` [PATCH 2/4] idmapd: Add graceful exit and resource cleanup Doug Nazar
2020-07-23 17:56 ` Steve Dickson
2020-07-23 18:25 ` Doug Nazar
2020-07-23 19:16 ` Steve Dickson
2020-07-22 5:53 ` [PATCH 3/4] idmapd: Fix client mode support Doug Nazar
2020-07-22 5:53 ` [PATCH 4/4] nfsidmap: Allow overriding location of method libraries Doug Nazar
2020-07-27 14:42 ` [PATCH 0/4] nfs-utils patches Steve Dickson
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=20200722055354.28132-1-nazard@nazar.ca \
--to=nazard@nazar.ca \
--cc=linux-nfs@vger.kernel.org \
/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).