From: Vince Busam <vbusam@google.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fix typo on __rpc_purge_upcall
Date: Mon, 21 Nov 2005 14:59:40 -0800 [thread overview]
Message-ID: <4382515C.9020200@google.com> (raw)
In-Reply-To: <1132612440.8011.7.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> On Mon, 2005-11-21 at 13:51 -0800, Vince Busam wrote:
>
>>Trond Myklebust wrote:
>>
>>>On Mon, 2005-11-21 at 11:51 -0800, Vince Busam wrote:
>>>
>>>http://client.linux-nfs.org/Linux-2.6.x/2.6.15-rc2/linux-2.6.15-06-rpc_pipe_fix_cleanup.dif
>>>
>>
>>That looks good to me. After testing this fix for a week, I haven't gotten an Oops, but
>>the system still locks up. The only relevant log message is about an upcall timing out.
>>
>>Nov 20 00:19:00 dig kernel: RPC: AUTH_GSS upcall timed out.
>>Nov 20 00:19:00 dig kernel: Please check user daemon is running!
>
>
> What kernel is this? There was a patch from Steve that caused this type
> of behaviour in some 2.6.14 CITI_ALL patches. That patch has since been
> removed.
This is 2.6.13.4, with the __rpc_purge_upcall patch, linux-2.6.13-CITI_NFS4_ALL-1.dif, and
an ugly patch that I don't remember why I'm using.
--- linux-2.6.8/net/sunrpc/auth_gss/auth_gss.c 2004-08-13 22:36:57.000000000 -0700
+++ linux-2.6.8-new/net/sunrpc/auth_gss/auth_gss.c 2004-08-24 14:44:40.887239458 -0700
@@ -515,6 +515,8 @@
clnt = rpci->private;
auth = clnt->cl_auth;
+ if (auth == NULL)
+ return;
gss_auth = container_of(auth, struct gss_auth, rpc_auth);
spin_lock(&gss_auth->lock);
while (!list_empty(&gss_auth->upcalls)) {
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-11-21 23:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 19:51 [PATCH] Fix typo on __rpc_purge_upcall Vince Busam
2005-11-21 19:55 ` Trond Myklebust
2005-11-21 21:51 ` Vince Busam
2005-11-21 22:34 ` Trond Myklebust
2005-11-21 22:59 ` Vince Busam [this message]
2005-11-21 23:07 ` Trond Myklebust
2005-11-28 18:16 ` Vince Busam
2005-11-28 18:52 ` Trond Myklebust
2005-12-05 21:03 ` Vince Busam
2005-12-12 18:57 ` Vince Busam
2005-12-12 19:18 ` Trond Myklebust
2005-12-12 20:33 ` Vince Busam
2005-12-12 23:51 ` Trond Myklebust
2006-01-05 22:30 ` Vince Busam
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=4382515C.9020200@google.com \
--to=vbusam@google.com \
--cc=nfs@lists.sourceforge.net \
--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