All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Wenwu Hou <hwenwur@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Minchan Kim <minchan@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] kernfs: release kernfs_mutex before the inode allocation
Date: Tue, 30 Jun 2026 03:50:08 -1000	[thread overview]
Message-ID: <akPJkI9KV8nZbb8Y@slm.duckdns.org> (raw)
In-Reply-To: <akM3Z5nDt82RecXn@aa-HP-ProDesk>

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

  reply	other threads:[~2026-06-30 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 19:43 [RFC PATCH] kernfs: release kernfs_mutex before the inode allocation Minchan Kim
2021-11-16 19:49 ` Greg Kroah-Hartman
2021-11-16 21:36   ` Minchan Kim
2021-11-17  6:44     ` Greg Kroah-Hartman
2021-11-17  7:27       ` Minchan Kim
2021-11-17  7:39         ` Greg Kroah-Hartman
2021-11-17 21:43           ` Minchan Kim
2021-11-17 21:45         ` Tejun Heo
2021-11-17 22:13           ` Minchan Kim
2021-11-17 22:23             ` Tejun Heo
2021-11-18  1:55               ` Minchan Kim
2021-11-18 16:35                 ` Tejun Heo
2026-06-30  3:26   ` Wenwu Hou
2026-06-30 13:50     ` Tejun Heo [this message]
2026-07-01  1:26       ` Ian Kent
2026-06-30 14:30     ` Ian Kent
2026-07-02  2:28     ` Ian Kent

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=akPJkI9KV8nZbb8Y@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hwenwur@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.