From: Kees Cook <keescook@chromium.org>
To: Matthew Garrett <mjg59@google.com>
Cc: Linux-MM <linux-mm@kvack.org>,
Matthew Wilcox <willy@infradead.org>,
Alexander Potapenko <glider@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4] mm: Allow userland to request that the kernel clear memory on release
Date: Thu, 6 Jun 2019 15:45:08 -0700 [thread overview]
Message-ID: <201906061543.10940C6@keescook> (raw)
In-Reply-To: <CACdnJuvJcJ4Rkp7gBTwZ_r_9wKtu34Yko+E3yo07cwc53QrGGA@mail.gmail.com>
On Wed, Jun 05, 2019 at 11:26:03AM -0700, Matthew Garrett wrote:
> Any further feedback on this? Does it seem conceptually useful?
Hi!
I love this patch, and I think it can nicely combine with Alexander's
init_on_alloc/free series[1].
One thing I'd like to see changed is that the DONTWIPE call should
wipe the memory. That way, there is no need to "trust" child behavior.
The only way out of the WIPE flag is that the memory gets wiped.
[1] https://patchwork.kernel.org/patch/10967023/
--
Kees Cook
next prev parent reply other threads:[~2019-06-06 22:45 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
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 [this message]
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=201906061543.10940C6@keescook \
--to=keescook@chromium.org \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjg59@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 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.