All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Subject: Re: [PATCH] gssd: on krb5 upcall, have gssd send a more granular error code
Date: Tue, 12 Jan 2010 07:36:37 -0500	[thread overview]
Message-ID: <4B4C6CD5.9070703@RedHat.com> (raw)
In-Reply-To: <1262875355-4522-1-git-send-email-jlayton@redhat.com>



On 01/07/2010 09:42 AM, Jeff Layton wrote:
> Currently if a krb5 context expires, GSSAPI authenticated RPC calls
> start returning error (-EACCES in particular). This is bad when someone has
> a long running job that's doing filesystem ops on a krb5 authenticated NFS
> mount and just happens to forget to redo a 'kinit' in time.
> 
> The existing gssd always does a downcall with a '-1' error code if there
> are problems, and the kernel always ignores this error code. Begin to
> fix this by having gssd distinguish between someone that has no
> credcache at all, and someone who has an expired one. In the case where
> there is an existing credcache, have gssd downcall with an error code of
> -EKEYEXPIRED. If there's not a credcache, then downcall with an error of
> -EACCES.
> 
> We can then have the kernel use this error code to handle these
> situations differently.
> 
Committed...

steved.

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 14:42 [PATCH] gssd: on krb5 upcall, have gssd send a more granular error code Jeff Layton
2010-01-12 12:36 ` 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=4B4C6CD5.9070703@RedHat.com \
    --to=steved@redhat.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.