From: "J. Bruce Fields" <bfields@fieldses.org>
To: Mark Goodman <mgoodman@CSUA.Berkeley.EDU>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Let NFS3 krb5 mounts survive a krb5 ticket expiration
Date: Thu, 23 Sep 2004 09:19:06 -0400 [thread overview]
Message-ID: <20040923131906.GB15809@fieldses.org> (raw)
In-Reply-To: <415278CF.6010505@csua.berkeley.edu>
On Thu, Sep 23, 2004 at 12:18:39AM -0700, Mark Goodman wrote:
> In my environment, this patch lets NFS3 krb5 mounts survive a krb5
> ticket expiration. It applies to 2.6.9-rc2. Please consider applying.
See patches 2, 3, and 4 at
http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.9-rc2-1/
which should make it to mainline soon.
--Bruce Fields
> Signed-off-by: Mark Goodman <mgoodman@csua.berkeley.edu>
>
> --- linux-2.6.9-rc2/net/sunrpc/auth_gss/auth_gss.c.orig 2004-09-23
> 00:07:28.891626224 -0700
> +++ linux-2.6.9-rc2/net/sunrpc/auth_gss/auth_gss.c 2004-09-23
> 00:06:56.159602248 -0700
> @@ -742,6 +742,9 @@ gss_marshal(struct rpc_task *task, u32 *
> &verf_buf, &mic);
> if(maj_stat != 0){
> printk("gss_marshal: gss_get_mic FAILED (%d)\n", maj_stat);
> + if (maj_stat == GSS_S_CONTEXT_EXPIRED) {
> + cred->cr_flags |= RPCAUTH_CRED_DEAD;
> + }
> goto out_put_ctx;
> }
> p = xdr_encode_opaque(p, NULL, mic.len);
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-09-23 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 7:18 [PATCH] Let NFS3 krb5 mounts survive a krb5 ticket expiration Mark Goodman
2004-09-23 13:19 ` J. Bruce Fields [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=20040923131906.GB15809@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgoodman@CSUA.Berkeley.EDU \
--cc=trond.myklebust@fys.uio.no \
/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