From: Chuck Lever via Bugspray Bot <bugbot@kernel.org>
To: trondmy@kernel.org, linux-nfs@vger.kernel.org, cel@kernel.org,
anna@kernel.org, jlayton@kernel.org
Subject: Re: deploying both NFS client and server on the same machine trigger hungtask
Date: Wed, 04 Dec 2024 15:30:07 +0000 [thread overview]
Message-ID: <20241204-b219550c3-c55f880f3db4@bugzilla.kernel.org> (raw)
In-Reply-To: <20241203-b219550c0-abf5589a5df5@bugzilla.kernel.org>
Chuck Lever writes via Kernel.org Bugzilla:
I think we had better be clear here.
Running an NFS client and server on the same system is fine, and "supported". It's also OK for an NFS client and server running on the same physical host but in separate guests (or one on the host and one in a guest).
What is problematic (ie, deadlock-prone) is when that client mounts the NFS server running on the same kernel. This includes container configurations, since containers share the same kernel and memory resources.
I assume that the deadlock reported in this bug occurs when a Linux NFS client mounts the NFS server running in the same kernel.
View: https://bugzilla.kernel.org/show_bug.cgi?id=219550#c3
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2024-12-04 15:29 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 [this message]
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
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=20241204-b219550c3-c55f880f3db4@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@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