From: Jiri Slaby <jslaby@suse.cz>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, ML netdev <netdev@vger.kernel.org>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix infinite loop in gss_create_upcall()
Date: Tue, 12 Apr 2011 20:05:33 +0200 [thread overview]
Message-ID: <4DA4946D.5020403@suse.cz> (raw)
In-Reply-To: <4DA48EB0.40600@netapp.com>
On 04/12/2011 07:41 PM, Bryan Schumaker wrote:
> On 04/11/2011 05:08 PM, Jiri Slaby wrote:
>>
>> Sorry for an extra message. I've just found out that there appears
>> messages in dmesg:
>> [ 58.656048] RPC: AUTH_GSS upcall timed out.
>> [ 58.656050] Please check user daemon is running.
>> [ 88.656065] RPC: AUTH_GSS upcall timed out.
>> [ 88.656068] Please check user daemon is running.
>> [ 118.656077] RPC: AUTH_GSS upcall timed out.
>> [ 118.656080] Please check user daemon is running.
>> [ 148.656049] RPC: AUTH_GSS upcall timed out.
>> [ 148.656052] Please check user daemon is running.
>> [ 178.656046] RPC: AUTH_GSS upcall timed out.
>> [ 178.656049] Please check user daemon is running.
>>
>>
>> I instrumented the code and it's stuck with trying RPC_AUTH_GSS_KRB5.
>>
>> I don't use GSS at all.
>>
>> regards,
>
> Does this patch help?
>
> - Bryan
>
>
>
> There can be an infinite loop if gss_create_upcall() is called without
> the userspace program running. To prevent this, we return -EACCES if
> we notice that pipe_version hasn't changed (indicating that the pipe
> has not been opened).
Yes, it fixes the problem. But it waits 15s before it times out. This is
inacceptable for automounted NFS dirs.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2011-04-12 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201103312224.p2VMOA5g000983@imap1.linux-foundation.org>
2011-04-02 8:56 ` nfs client doesn't work [was: mmotm 2011-03-31-14-48 uploaded] Jiri Slaby
[not found] ` <1302122693.16786.0.camel@lade.trondhjem.org>
2011-04-07 6:42 ` Jiri Slaby
2011-04-11 20:40 ` Jiri Slaby
2011-04-11 20:40 ` Jiri Slaby
2011-04-11 21:08 ` Jiri Slaby
2011-04-12 17:41 ` [PATCH] NFS: Fix infinite loop in gss_create_upcall() Bryan Schumaker
2011-04-12 18:05 ` Jiri Slaby [this message]
2011-04-12 18:31 ` Trond Myklebust
2011-04-12 18:34 ` Jiri Slaby
2011-04-12 18:38 ` Trond Myklebust
2011-04-12 18:43 ` Bryan Schumaker
2011-04-12 18:52 ` Jiri Slaby
2011-04-13 20:42 ` Bryan Schumaker
2011-04-14 20:37 ` Jiri Slaby
2011-04-14 21:21 ` Trond Myklebust
2011-04-14 21:30 ` Jiri Slaby
2011-04-11 20:56 ` nfs client doesn't work [was: mmotm 2011-03-31-14-48 uploaded] Bryan Schumaker
2011-04-11 21:19 ` Jiri Slaby
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=4DA4946D.5020403@suse.cz \
--to=jslaby@suse.cz \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bjschuma@netapp.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).