All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Dauchy <wdauchy@gmail.com>
To: bjschuma@netapp.com
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/3] NFS: return -ENOKEY when the upcall fails to map the name
Date: Fri, 10 Aug 2012 12:10:15 +0200	[thread overview]
Message-ID: <CAJ75kXZizTP-6KuQj85UeHV1-jYCXGnWMTQO7jDsOtJdfh9bDg@mail.gmail.com> (raw)
In-Reply-To: <1344535551-4412-2-git-send-email-bjschuma@netapp.com>

On Thu, Aug 9, 2012 at 8:05 PM,  <bjschuma@netapp.com> wrote:
> This allows the normal error-paths to handle the error, rather than
> making a special call to complete_request_key() just for this instance.
>
> Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>

Tested-by: William Dauchy <wdauchy@gmail.com>
Cc: stable@vger.kernel.org

-- 
William

  reply	other threads:[~2012-08-10 10:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 18:05 [PATCH 1/3] NFS: Clear key construction data if the idmap upcall fails bjschuma
2012-08-09 18:05 ` [PATCH 2/3] NFS: return -ENOKEY when the upcall fails to map the name bjschuma
2012-08-10 10:10   ` William Dauchy [this message]
2012-08-10 11:04   ` William Dauchy
2012-08-09 18:05 ` [PATCH 3/3] NFS: Use kzalloc() instead of kmalloc() in the idmapper bjschuma
2012-08-10 10:10   ` William Dauchy
2012-08-10 16:16     ` Myklebust, Trond
2012-08-12 17:48       ` William Dauchy
2012-08-10 10:09 ` [PATCH 1/3] NFS: Clear key construction data if the idmap upcall fails William Dauchy
2012-08-16 13:45   ` William Dauchy
2012-08-16 15:07     ` William Dauchy
2012-08-16 15:21       ` Bryan Schumaker
2012-08-16 15:34         ` William Dauchy

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=CAJ75kXZizTP-6KuQj85UeHV1-jYCXGnWMTQO7jDsOtJdfh9bDg@mail.gmail.com \
    --to=wdauchy@gmail.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --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.