From: Neil Brown via Bugspray Bot <bugbot@kernel.org>
To: trondmy@hammerspace.com, jlayton@kernel.org, anna@kernel.org,
linux-nfs@vger.kernel.org, cel@kernel.org, trondmy@kernel.org
Subject: Re: deploying both NFS client and server on the same machine trigger hungtask
Date: Sun, 08 Dec 2024 21:20:10 +0000 [thread overview]
Message-ID: <20241208-b219550c6-03553d0a9ee6@bugzilla.kernel.org> (raw)
In-Reply-To: <20241203-b219550c0-abf5589a5df5@bugzilla.kernel.org>
Neil Brown writes via Kernel.org Bugzilla:
I think this bug was fixed in Linux v6.7 by
Commit ca1d36b82394 ("mm: shrinker: make global slab shrink lockless")
The shrinker_rwsem has been replaced by shrinker_mutex and is no longer held while shrinking slabs. So if nfs4_evict_inode() blocks on a non-responsive server it may block one vmscan thread, but shouldn't cause any blockage outside of that filesystem.
You were using v5.10 which is 4 years old next week. Please re-test with a newer kernel.
(And I think we *should* consider loop-back NFS to be supported in the sense that we will make a reasonable effort to fix any problems that are reported)
View: https://bugzilla.kernel.org/show_bug.cgi?id=219550#c6
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
prev parent reply other threads:[~2024-12-08 21:19 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
2024-12-08 21:20 ` Neil Brown via Bugspray Bot [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=20241208-b219550c6-03553d0a9ee6@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
--cc=trondmy@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