From: Michal Hocko <mhocko@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
David Rientjes <rientjes@google.com>,
Matthew Wilcox <willy@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <guro@fb.com>, Rik van Riel <riel@surriel.com>,
Christian Brauner <christian@brauner.io>,
Oleg Nesterov <oleg@redhat.com>,
Tim Murray <timmurray@google.com>,
linux-api@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@android.com>,
Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process
Date: Wed, 18 Nov 2020 20:10:21 +0100 [thread overview]
Message-ID: <20201118154334.GT12284@dhcp22.suse.cz> (raw)
In-Reply-To: <20201113181632.6d98489465430a987c96568d@linux-foundation.org>
On Fri 13-11-20 18:16:32, Andrew Morton wrote:
[...]
> It's all sounding a bit painful (but not *too* painful). But to
> reiterate, I do think that adding the ability for a process to shoot
> down a large amount of another process's memory is a lot more generally
> useful than tying it to SIGKILL, agree?
I am not sure TBH. Is there any reasonable usecase where uncoordinated
memory tear down is OK and a target process which is able to see the
unmapped memory?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-11-18 19:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 17:34 [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process Suren Baghdasaryan
2020-11-13 23:55 ` Andrew Morton
2020-11-14 0:06 ` Suren Baghdasaryan
2020-11-14 1:00 ` Andrew Morton
2020-11-14 1:09 ` Suren Baghdasaryan
2020-11-14 1:18 ` Andrew Morton
2020-11-14 1:57 ` Suren Baghdasaryan
2020-11-14 2:16 ` Andrew Morton
2020-11-14 2:51 ` Suren Baghdasaryan
2020-11-16 23:24 ` Minchan Kim
2020-11-18 19:10 ` Michal Hocko [this message]
2020-11-18 19:22 ` Suren Baghdasaryan
2020-11-18 19:32 ` Michal Hocko
2020-11-18 19:51 ` Suren Baghdasaryan
2020-11-18 19:55 ` Suren Baghdasaryan
2020-11-19 0:13 ` Suren Baghdasaryan
2020-11-24 5:45 ` Suren Baghdasaryan
2020-11-18 10:32 ` Christian Brauner
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=20201118154334.GT12284@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=christian@brauner.io \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@android.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=oleg@redhat.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=surenb@google.com \
--cc=timmurray@google.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).