All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: [PATCH 1/4] sunrpc: parse and return errors reported by gssd
Date: Thu, 07 Jan 2010 14:11:56 -0500	[thread overview]
Message-ID: <1262891516.3309.14.camel@localhost> (raw)
In-Reply-To: <1262875325-4488-2-git-send-email-jlayton@redhat.com>

On Thu, 2010-01-07 at 09:42 -0500, Jeff Layton wrote:

> @@ -646,6 +652,7 @@ gss_pipe_downcall(struct file *filp, const char __user *src, size_t mlen)
>  		err = PTR_ERR(p);
>  		switch (err) {
>  		case -EACCES:
> +		case -EKEYEXPIRED:
>  			gss_msg->msg.errno = err;
>  			err = mlen;
>  			break;

              ^^^^^^^^^^^^^^^^^^^^^ This doesn't appear to want to apply
to mainline. Did you perhaps skip a patch?

Trond

  reply	other threads:[~2010-01-07 19:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 14:42 [PATCH 0/4] sunrpc/nfs: better handling for expired krb5 credentials Jeff Layton
2010-01-07 14:42 ` [PATCH 1/4] sunrpc: parse and return errors reported by gssd Jeff Layton
2010-01-07 19:11   ` Trond Myklebust [this message]
2010-01-07 19:21     ` Jeff Layton
2010-01-07 19:39       ` Trond Myklebust
2010-01-07 14:42 ` [PATCH 2/4] nfs4: handle -EKEYEXPIRED errors from RPC layer Jeff Layton
2010-01-07 14:42 ` [PATCH 3/4] nfs: handle NFSv3 -EKEYEXPIRED errors as we would -EJUKEBOX Jeff Layton
2010-01-07 14:42 ` [PATCH 4/4] nfs: handle NFSv2 -EKEYEXPIRED returns from RPC layer appropriately Jeff Layton
2010-01-07 19:48   ` Jeff Layton
2010-01-08 17:17   ` Jeff Layton

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=1262891516.3309.14.camel@localhost \
    --to=trond.myklebust@netapp.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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.