From: Steve Dickson <SteveD@redhat.com>
To: Benjamin Coddington <bcodding@uvm.edu>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] nfsidmap: a keyringer - 2nd try
Date: Tue, 25 Mar 2014 10:44:29 -0400 [thread overview]
Message-ID: <5331964D.10505@RedHat.com> (raw)
In-Reply-To: <cover.1395710586.git.root@hobo-dev.uvm.edu>
On 03/24/2014 09:23 PM, Benjamin Coddington wrote:
> 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.
I'm not going to take these for upstream since I don't think they
are needed... If that turns out not to be the case, we can add it later...
steved.
>
> 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(-)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2014-03-25 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 1:23 [PATCH 0/2] nfsidmap: a keyringer - 2nd try Benjamin Coddington
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 ` Steve Dickson [this message]
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=5331964D.10505@RedHat.com \
--to=steved@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.