From: Michal Hocko <mhocko@kernel.org>
To: Matthew Garrett <mjg59@google.com>
Cc: linux-mm@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH V2] mm: Allow userland to request that the kernel clear memory on release
Date: Fri, 26 Apr 2019 07:25:20 +0200 [thread overview]
Message-ID: <20190426052520.GB12337@dhcp22.suse.cz> (raw)
In-Reply-To: <CACdnJuutwmBn_ASY1N1+ZK8g4MbpjTnUYbarR+CPhC5BAy0oZA@mail.gmail.com>
On Thu 25-04-19 13:39:01, Matthew Garrett wrote:
> On Thu, Apr 25, 2019 at 5:37 AM Michal Hocko <mhocko@kernel.org> wrote:
> > Besides that you inherently assume that the user would do mlock because
> > you do not try to wipe the swap content. Is this intentional?
>
> Yes, given MADV_DONTDUMP doesn't imply mlock I thought it'd be more
> consistent to keep those independent.
Do we want to fail madvise call on VMAs that are not mlocked then? What
if the munlock happens later after the madvise is called?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-04-26 5:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 19:14 [PATCH] mm: Allow userland to request that the kernel clear memory on release Matthew Garrett
2019-04-24 19:28 ` Matthew Wilcox
2019-04-24 19:33 ` Matthew Garrett
2019-04-24 19:33 ` Matthew Garrett
2019-04-24 20:20 ` Matthew Wilcox
2019-04-24 20:22 ` Matthew Garrett
2019-04-24 20:22 ` Matthew Garrett
2019-04-24 21:10 ` [PATCH V2] " Matthew Garrett
2019-04-25 12:14 ` Michal Hocko
2019-04-25 12:37 ` Michal Hocko
2019-04-25 20:39 ` Matthew Garrett
2019-04-25 20:39 ` Matthew Garrett
2019-04-26 5:25 ` Michal Hocko [this message]
2019-04-26 18:08 ` Matthew Garrett
2019-04-26 18:08 ` Matthew Garrett
2019-04-29 21:44 ` Michal Hocko
2019-04-25 12:40 ` Vlastimil Babka
2019-04-25 20:45 ` Matthew Garrett
2019-04-25 20:45 ` Matthew Garrett
2019-04-25 12:42 ` Jann Horn
2019-04-25 12:42 ` Jann Horn
2019-04-25 20:43 ` Matthew Garrett
2019-04-25 20:43 ` Matthew Garrett
2019-04-26 5:31 ` Michal Hocko
2019-04-26 13:33 ` Jann Horn
2019-04-26 13:33 ` Jann Horn
2019-04-26 13:47 ` Michal Hocko
2019-04-26 14:03 ` Jann Horn
2019-04-26 14:03 ` Jann Horn
2019-04-26 14:08 ` Michal Hocko
2019-04-25 22:58 ` [PATCH V3] " Matthew Garrett
2019-04-25 22:58 ` Matthew Garrett
2019-04-26 7:45 ` Vlastimil Babka
2019-04-26 18:10 ` Matthew Garrett
2019-04-26 18:10 ` Matthew Garrett
2019-04-29 19:36 ` [PATCH V4] " Matthew Garrett
2019-06-05 18:26 ` Matthew Garrett
2019-06-06 22:45 ` Kees Cook
2019-04-25 15:32 ` [PATCH] " Christopher Lameter
2019-04-25 15:32 ` Christopher Lameter
2019-04-25 20:29 ` Matthew Garrett
2019-04-25 20:29 ` Matthew Garrett
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=20190426052520.GB12337@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjg59@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.