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)
