From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/6] nfsidmap enhancements
Date: Wed, 05 Aug 2015 10:45:23 -0400 [thread overview]
Message-ID: <20150805143258.13266.92369.stgit@manet.1015granger.net> (raw)
Add "-d" and "-l" options, and clean up some error handling
problems.
I've decided to think more about the mechanism which sets the NFSv4
domain. Neither conf_ nor libnfsidmap has any support for modifying
a configuration file. The naive approach is to open-code editing the
configuration file, which is kind of ugly.
Build and basic operational testing on Fedora 22 and on RHEL 6
passes. Steve, IMO these are ready to be merged.
Changes since the first version:
- Tested
- Various small clean ups
- "else" is gone
---
Chuck Lever (6):
nfsidmap: Display the effective NFSv4 domain name
nfsidmap: Use find_key_by_type_and_desc() if available
nfsidmap: List cached ID mapping results
nfsidmap: Fix error handling in id_lookup()
nfsidmap: Fix error handling in name_lookup()
nfsidmap: Clean up other exit status cases
utils/nfsidmap/nfsidmap.c | 299 ++++++++++++++++++++++++++++++-------------
utils/nfsidmap/nfsidmap.man | 74 +++++++++--
2 files changed, 271 insertions(+), 102 deletions(-)
--
Chuck Lever
next reply other threads:[~2015-08-05 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 14:45 Chuck Lever [this message]
2015-08-05 14:45 ` [PATCH v2 1/6] nfsidmap: Display the effective NFSv4 domain name Chuck Lever
2015-08-05 14:45 ` [PATCH v2 2/6] nfsidmap: Use find_key_by_type_and_desc() if available Chuck Lever
2015-08-05 14:45 ` [PATCH v2 3/6] nfsidmap: List cached ID mapping results Chuck Lever
2015-08-05 14:46 ` [PATCH v2 4/6] nfsidmap: Fix error handling in id_lookup() Chuck Lever
2015-08-05 14:46 ` [PATCH v2 5/6] nfsidmap: Fix error handling in name_lookup() Chuck Lever
2015-08-05 14:46 ` [PATCH v2 6/6] nfsidmap: Clean up other exit status cases Chuck Lever
2015-09-16 19:08 ` [PATCH v2 0/6] nfsidmap enhancements 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=20150805143258.13266.92369.stgit@manet.1015granger.net \
--to=chuck.lever@oracle.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).