All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Trond.Myklebust@netapp.com
Cc: dhowells@redhat.com, bjschuma@netapp.com,
	linux-nfs@vger.kernel.org, steved@redhat.com, jlayton@redhat.com
Subject: Re: [PATCH 2/2] NFS: Combine the idmapper key types
Date: Wed, 25 Jul 2012 16:57:05 +0100	[thread overview]
Message-ID: <24518.1343231825@warthog.procyon.org.uk> (raw)
In-Reply-To: <20120725155347.24392.44505.stgit@warthog.procyon.org.uk>


Hi Trond,

David Howells <dhowells@redhat.com> wrote:

> The NFS idmapper has two key types (normal and legacy) but should only use one
> if it can - otherwise it risks having twice as many keys as it would otherwise
> need.
> 
> Get rid of the legacy key type and have the normal key type have a
> .request_key() op.  The choice of which instantiation method is then made by
> the upcaller, in order:
> 
>  (1) If there's no auxdata, the normal method is called, invoking
>      /sbin/request-key.
> 
>  (2) If there's something attached to the idmapper pipe (rpc.idmapd) then use
>      that.
> 
>  (3) Fall back to (1).
> 
> Note that this does change the prioritisation of normal vs legacy if both are
> available.

I'm not sure whether this will be a problem, so it needs careful
consideration.

David

  reply	other threads:[~2012-07-25 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25 15:53 [PATCH 1/2] NFS: Fix a number of bugs in the idmapper David Howells
2012-07-25 15:53 ` [PATCH 2/2] NFS: Combine the idmapper key types David Howells
2012-07-25 15:57   ` David Howells [this message]
2012-07-25 18:15   ` Bryan Schumaker
2012-07-31 14:45     ` David Howells
  -- strict thread matches above, loose matches on Subject: below --
2012-07-31 14:42 [PATCH 1/2] NFS: Fix a number of bugs in the idmapper David Howells
2012-07-31 14:42 ` [PATCH 2/2] NFS: Combine the idmapper key types David Howells
2012-07-31 14:54   ` Myklebust, Trond
2012-07-31 15:05     ` David Howells

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=24518.1343231825@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --cc=jlayton@redhat.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 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.