From: Benjamin Coddington <bcodding@uvm.edu>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfsidmap: a keyringer - 2nd try
Date: Mon, 24 Mar 2014 21:23:06 -0400 [thread overview]
Message-ID: <cover.1395710586.git.root@hobo-dev.uvm.edu> (raw)
I took a second stab at this since it looks like fixing the keyrings is
probably the way to go. This time through, the nfsidmap creates the
keyrings ad-hoc as they fill up instead of taking new command-line
parameters. It also explicitly sets the permissions on the new keyrings, so
they should be able to be cleaned up in later kernels - though I haven't
tested that myself.
Ben
Benjamin Coddington (2):
nfsidmap: Match names with kernel default keyring
nfsidmap: Create id_resolver child keyrings
utils/nfsidmap/nfsidmap.c | 76 ++++++++++++++++++++++++++++++++++++---------
1 files changed, 61 insertions(+), 15 deletions(-)
next reply other threads:[~2014-03-25 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 1:23 Benjamin Coddington [this message]
2014-03-24 23:56 ` [PATCH 1/2] nfsidmap: Match names with kernel default keyring Benjamin Coddington
2014-03-25 1:06 ` [PATCH 2/2] nfsidmap: Create id_resolver child keyrings Benjamin Coddington
2014-03-25 14:44 ` [PATCH 0/2] nfsidmap: a keyringer - 2nd try 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=cover.1395710586.git.root@hobo-dev.uvm.edu \
--to=bcodding@uvm.edu \
--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).