From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B3A3A36C9D5 for ; Tue, 30 Jun 2026 13:50:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782827410; cv=none; b=Qpopeo+X/V/EPq34Sw0Ytj7m3/wfgItFjbdC+v3jk8d/VYznsTsNsRZITp0y3vXzXt2MNLw4+gmE3kvOsWyp3O3B8PhCf3CFKhWshz7S6Lk6FnPz8LbLKi00Ogh1ZZSdTfG/sKT2qoycy/T1OsNbvPgY7Mls94ka7bOi0nid/Bc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782827410; c=relaxed/simple; bh=lhFMHO14fTDrf/bTLZdgKiBbHmZlPqwLVc1AE0oM6qY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=K51686EuiNPJ/zpE6ySeyQrfr/xymZMS1NSjWjFrdZ7MJ6S/D16e0ddsvju5ubSfGHXM7KAiLT2k23YUmKdbTv6aMJpb65rAXFd1RfGX1LCTywwU9x8YWEpthVXS0X5oRsOUo92IrcUhx9/Nep3yM5Zw5K0pMyTUk2I24sglpoc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ajNgmU2c; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ajNgmU2c" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 23CE61F000E9; Tue, 30 Jun 2026 13:50:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782827409; bh=RdYx4thOkxbuClB32iG6ZfU0zWJasSHS+gGz+MXRUhk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ajNgmU2cLTgYx54IR/otbuwR01Wnv6sdq350E24IpsnT990bwWEmNWHMqNqbolLzF uVwgyQEoIhNtubm5SorUC0+bTn9ZzuwUd6yuWlInyc65TVNUHYH/z1R9Vl+7Mh0mdY cmmfS9XhyJqIUhoeqR9uoTaaqFpDuffXX2WIC3pC2IR+A5BniBOQOwpmkT+71xc0gH Zk4fqWObwq+gB5jbPSFVr2kUJGURijTv33jTbnM05d4UBNvRUwi47Kae0Fn+21jvoh SIEyBJy/0rpQhhYuJS9kxafO36eMk08qG7Ow44WzJWF39an/BLQlDB5Y/JntRkLYUC fizauQmkMJe4g== Date: Tue, 30 Jun 2026 03:50:08 -1000 From: Tejun Heo To: Wenwu Hou Cc: Greg Kroah-Hartman , Minchan Kim , LKML Subject: Re: [RFC PATCH] kernfs: release kernfs_mutex before the inode allocation Message-ID: References: <20211116194317.1430399-1-minchan@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hello, On Tue, Jun 30, 2026 at 11:26:31AM +0800, Wenwu Hou wrote: ... > In our real-world case, thousands of nodejs processes hit the cgroup memory > limit and sleep on the OOM path, runc gets blocked, and consequently the node > remains in an unschedulable state for many hours. I don't think we can work around thousands of processes stalling in OOM path with kernfs locking changes. There are better ways to manage memory pressure. Please look into memory.high and PSI driven userspace OOM handling. Thanks. -- tejun