From: NeilBrown <neilb@suse.com>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: Linux List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Revert "SUNRPC: xs_sock_mark_closed() does not need to trigger socket autoclose"
Date: Thu, 04 Aug 2016 12:35:50 +1000 [thread overview]
Message-ID: <871t25p8ft.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <A059233E-0EFD-472A-9CCB-7BE8411BFC03@primarydata.com>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
On Thu, Aug 04 2016, Trond Myklebust wrote:
>> On Aug 3, 2016, at 19:33, NeilBrown <neilb@suse.com> wrote:
>>
>>
>> This reverts commit 4b0ab51db32eba0f48b7618254742f143364a28d.
>>
>> This change causes 'rpc.nfsd' to hang for long time if rpcbind is not
>> available.
>> If
>> --no-nfs-version 2 --no-nfs-version 3
>> is given, the delay is about 6.5 minutes. When trying to register
>> all versions, the delay is over half an hour.
>> Before this commit, and after reverting it, nfsd fails (when v3 is
>> requested) or succeeds (when only v4 is requested) immediately.
>>
>> Signed-off-by: NeilBrown <neilb@suse.com>
>> ---
>> net/sunrpc/xprtsock.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
>> index 111767ab124a..2a938055e95b 100644
>> --- a/net/sunrpc/xprtsock.c
>> +++ b/net/sunrpc/xprtsock.c
>> @@ -795,6 +795,7 @@ static void xs_sock_mark_closed(struct rpc_xprt *xprt)
>> xs_sock_reset_connection_flags(xprt);
>> /* Mark transport as closed and wake up all pending tasks */
>> xprt_disconnect_done(xprt);
>> + xprt_force_disconnect(xprt);
>> }
>>
>
> If there is an outstanding request, then _that_ is supposed to redrive the connection. Why is the xprt_disconnect_done() not functioning as per the comment above it?
No idea, sorry. I haven't tried to follow though exactly what is
happening.
The symptom is trivial to reproduce:
rpc.nfsd 0
killall rpcbind
rpc.nfsd 8
This will either complete immediately with kernel log messages, or block
for a long time.
I might try to figure out what is happening, but I suspect there are
others who know this code a lot better than I do.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-08-04 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 23:33 [PATCH] Revert "SUNRPC: xs_sock_mark_closed() does not need to trigger socket autoclose" NeilBrown
2016-08-04 0:01 ` Trond Myklebust
2016-08-04 2:35 ` NeilBrown [this message]
2016-08-10 2:05 ` NeilBrown
2016-11-18 4:48 ` NeilBrown
2016-11-18 14:31 ` Trond Myklebust
2016-11-21 3:24 ` NeilBrown
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=871t25p8ft.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@primarydata.com \
/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).