From: David Howells <dhowells@redhat.com>
To: Benjamin Coddington <bcodding@uvm.edu>
Cc: dhowells@redhat.com, Steve Dickson <SteveD@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsidmap: use multiple child keyrings
Date: Tue, 25 Mar 2014 13:30:45 +0000 [thread overview]
Message-ID: <9576.1395754245@warthog.procyon.org.uk> (raw)
In-Reply-To: <8D885171-9D19-4E78-BC2F-D5AC906D7A3B@uvm.edu>
Benjamin Coddington <bcodding@uvm.edu> wrote:
> Yep, I'm aware of that - but unless RH backports this fix (which I was told
> is not going to happen) or uses this multiple keyring nfsidmap approach,
> things are going to stay broken in RHEL6.
Backporting the patches to RHEL-6 is a bit tricky as the contents of the key
struct changed as did some of the internal interface functions. It would be
possible to isolate the changes in the keyring payload struct - but we'd have
to hope no drivers out there access the keyring payload directly.
David
prev parent reply other threads:[~2014-03-25 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 21:08 [PATCH] nfsidmap: use multiple child keyrings Benjamin Coddington
2014-03-24 17:00 ` Steve Dickson
2014-03-24 18:00 ` Benjamin Coddington
2014-03-24 19:51 ` Steve Dickson
2014-03-24 21:03 ` Benjamin Coddington
2014-03-24 21:22 ` Steve Dickson
2014-03-24 22:10 ` Anna Schumaker
2014-03-24 23:57 ` Steve Dickson
2014-03-25 0:15 ` Benjamin Coddington
2014-03-25 9:35 ` David Howells
2014-03-25 12:49 ` Benjamin Coddington
2014-03-25 9:29 ` David Howells
2014-03-25 10:41 ` Steve Dickson
2014-03-25 9:34 ` David Howells
2014-03-25 12:56 ` Benjamin Coddington
2014-03-25 13:30 ` David Howells [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=9576.1395754245@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=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 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).