Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 98E10C54EED for ; Mon, 30 Jan 2023 10:10:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235415AbjA3KKw (ORCPT ); Mon, 30 Jan 2023 05:10:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46110 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233298AbjA3KKv (ORCPT ); Mon, 30 Jan 2023 05:10:51 -0500 Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E23766EB5; Mon, 30 Jan 2023 02:10:50 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 55EB75C00BF; Mon, 30 Jan 2023 05:10:50 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 30 Jan 2023 05:10:50 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1675073450; x=1675159850; bh=QPmaKWErOb HkxJKtSJxn4Y5wlbv/BaNd6xEYn+UsHbM=; b=P+gH9Ba6/DyA6PSs63/IOMttKh 9hC6WqvOWDyIuMlC15RpVFOS1KgbmbVh990RCyjR2t+M+TSnaBvrsA5HiSdsdwkU Q5uQRoMuAdq3za2TWrFWjQ8qWiXB7sFc8k5ZCnBbhd/z1HmTIf55+xnpGwbT3wUm SgsRl8MffYsrRvKWIbXx3A3t6faaR5EnG8DHgz2Te6qPn/FC61VqU3BH4f6jQ4so vkgSqp37a5kXtOLGXyvcwFImC9WJzZ8j4JAWc3scW8kE3IKEHLVwT1Y7LD/k2Xhf f8iTypc8K2PL5jvORCkcgHHhgQjEa0bFT47BoivmqmSK9hNYQtd0GdsO9+7A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1675073450; x=1675159850; bh=QPmaKWErObHkxJKtSJxn4Y5wlbv/ BaNd6xEYn+UsHbM=; b=rojJCwKzG9kPamWKFf+0y2mpW+n0+tE8MV41T7Qmx3w8 drxeLJ4qBfv09lKg7IvwnCF2dDsjAaqGnNoWysYeM61EvlCPYmCr2WxyH4MvasMy WxAowF9nl2G+2vuMdA20naZbe/ZX+EH+J0g5IzDBqlIskmtt6KbGH970IP535YzL W7gzvjaP1Z6bRIZiL8o9uV4+hi8dma85fJAPguA679W/RhDu/Gzx2ggmMVfYcRht Ch8n0LxdrlwjyztENSdzCfwRGm/XS019foKtuvkDrAQc/+8bmJaboPfX8slt8KAZ OF242WmgKDb2z/f7+iqX1kS2Vd2n8WZJI7y6dZx5BA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudefvddgudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepheegvd evvdeljeeugfdtudduhfekledtiefhveejkeejuefhtdeufefhgfehkeetnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorg hhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 Jan 2023 05:10:49 -0500 (EST) Date: Mon, 30 Jan 2023 11:10:46 +0100 From: Greg KH To: Chuck Lever III Cc: Nikos Tsironis , linux-stable , Bruce Fields , Linux NFS Mailing List , Trond Myklebust Subject: Re: [PATCH 5.4 0/1] nfsd: Ensure knfsd shuts down when the "nfsd" pseudofs is unmounted Message-ID: References: <20230123152822.868326-1-ntsironis@arrikto.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Mon, Jan 23, 2023 at 03:42:55PM +0000, Chuck Lever III wrote: > > > > On Jan 23, 2023, at 10:28 AM, Nikos Tsironis wrote: > > > > The bug that upstream commit c6c7f2a84da45 ("nfsd: Ensure knfsd shuts > > down when the "nfsd" pseudofs is unmounted") fixes in kernel v5.13 > > exists in kernel v5.4 too. > > > > That is, knfsd threads are left behind once the nfsd pseudofs is > > unmounted, e.g. when the container is killed. > > > > I backported the patch to kernel v5.4, and tested it. > > Nikos, thanks for taking care of this! Both now queued up, thanks. greg k-h