public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna@kernel.org" <anna@kernel.org>,
	"cel@kernel.org" <cel@kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"jlayton@kernel.org" <jlayton@kernel.org>,
	"bugbot@kernel.org" <bugbot@kernel.org>
Subject: Re: deploying both NFS client and server on the same machine trigger hungtask
Date: Fri, 6 Dec 2024 08:55:13 +0000	[thread overview]
Message-ID: <f8e2ccbb2cd329ddb99282df4c7e668cbdb25545.camel@hammerspace.com> (raw)
In-Reply-To: <20241204-b219550c4-eb90fb494c92@bugzilla.kernel.org>

On Wed, 2024-12-04 at 15:45 +0000, Jeff Layton via Bugspray Bot wrote:
> Jeff Layton writes via Kernel.org Bugzilla:
>
> Li Lingfeng's analysis looks basically correct to me, though I think
> the nfsd_mutex is mostly a red-herring here.
>
> The client holds the shrinker rwsem and is trying to write back data.
> The server is trying to unregister a shrinker as part of server
> shutdown and has almost certainly stopped responding to requests at
> that point. The client is using hard RPCs, so it's going to retry the
> writeback indefinitely while holding the shrinker mutex, which will
> block server shutdown.
>
> I don't see a great way to fix this right offhand, though I wonder if
> localio might help mitigate this problem.
>
> View:
> https://bugzilla.kernel.org/show_bug.cgi?id=219550#c4
> You can reply to this message to join the discussion.

localio won't help with the task of returning a delegation, as per the
stack trace that was shown:
https://lore.kernel.org/linux-nfs/20241203-b219550c0-abf5589a5df5@bugzilla.kernel.org/

If the server is no longer responding to RPC calls, then the client
should probably just let the delegreturn call time out and expire after
2 lease periods.

--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2024-12-06  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  2:30 deploying both NFS client and server on the same machine triggle hungtask Li Lingfeng via Bugspray Bot
2024-12-03 14:18 ` Jeff Layton
2024-12-03 14:50   ` deploying both NFS client and server on the same machine trigger hungtask Chuck Lever via Bugspray Bot
2024-12-04 15:30 ` Chuck Lever via Bugspray Bot
2024-12-04 15:45 ` Jeff Layton via Bugspray Bot
2024-12-06  8:55   ` Trond Myklebust [this message]
2024-12-08 21:20 ` Neil Brown via Bugspray Bot

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=f8e2ccbb2cd329ddb99282df4c7e668cbdb25545.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna@kernel.org \
    --cc=bugbot@kernel.org \
    --cc=cel@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@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