From: Michal Hocko <mhocko@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan@kernel.org>,
hca@linux.ibm.com, linux-s390@vger.kernel.org, david@kernel.org,
brauner@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, surenb@google.com,
timmurray@google.com
Subject: Re: [PATCH v2] mm: process_mrelease: introduce PROCESS_MRELEASE_REAP_KILL flag
Date: Thu, 30 Apr 2026 17:32:40 +0200 [thread overview]
Message-ID: <afN2GBAjBSGlTgvA@tiehlicka> (raw)
In-Reply-To: <20260430074305.9d3389ed71af040acfe222de@linux-foundation.org>
On Thu 30-04-26 07:43:05, Andrew Morton wrote:
> On Wed, 29 Apr 2026 14:13:59 -0700 Minchan Kim <minchan@kernel.org> wrote:
>
> > Currently, process_mrelease() requires userspace to send a SIGKILL signal
> > prior to invocation. This separation introduces a scheduling race window
> > where the victim task may receive the signal and enter the exit path
> > before the reaper can invoke process_mrelease().
>
> Does process_mrelease() have a manpage? My googling was a fail.
It does. Very well hidden in 884a7e5964e06
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2026-04-30 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 21:13 [PATCH v2] mm: process_mrelease: introduce PROCESS_MRELEASE_REAP_KILL flag Minchan Kim
2026-04-30 9:55 ` Michal Hocko
2026-05-01 21:17 ` Minchan Kim
2026-05-04 7:51 ` Michal Hocko
2026-05-05 5:04 ` Minchan Kim
2026-05-05 9:30 ` Christian Brauner
2026-05-05 16:03 ` Michal Hocko
2026-05-05 17:59 ` Minchan Kim
2026-05-11 21:44 ` Minchan Kim
2026-05-13 6:45 ` Michal Hocko
2026-05-14 21:50 ` Minchan Kim
2026-05-15 14:12 ` Christian Brauner
2026-04-30 14:43 ` Andrew Morton
2026-04-30 15:32 ` Michal Hocko [this message]
2026-04-30 16:34 ` Andrew Morton
2026-04-30 17:24 ` Suren Baghdasaryan
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=afN2GBAjBSGlTgvA@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=surenb@google.com \
--cc=timmurray@google.com \
/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.