From: Florian Weimer <fweimer@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Rik van Riel <riel@redhat.com>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-kernel@vger.kernel.org, mike.kravetz@oracle.com,
linux-mm@kvack.org, colm@allcosts.net, akpm@linux-foundation.org,
keescook@chromium.org, luto@amacapital.net, wad@chromium.org,
mingo@kernel.org, dave.hansen@intel.com,
linux-api@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mm,fork,security: introduce MADV_WIPEONFORK
Date: Wed, 9 Aug 2017 14:42:51 +0200 [thread overview]
Message-ID: <8fe8040c-7595-ec09-6ce7-0da4fadc82c4@redhat.com> (raw)
In-Reply-To: <20170809095957.kv47or2w4obaipkn@node.shutemov.name>
On 08/09/2017 11:59 AM, Kirill A. Shutemov wrote:
> It's not obvious to me what would break if kernel would ignore
> MADV_DONTFORK or MADV_DONTDUMP.
Ignoring MADV_DONTDUMP could cause secrets to be written to disk,
contrary to the expected security policy of the system.
Thanks,
Florian
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-08-09 12:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170806140425.20937-1-riel@redhat.com>
2017-08-07 13:22 ` [PATCH v2 0/2] mm,fork,security: introduce MADV_WIPEONFORK Michal Hocko
[not found] ` <20170807132257.GH32434-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-07 13:46 ` Michal Hocko
2017-08-07 14:19 ` Florian Weimer
2017-08-10 13:06 ` Michal Hocko
2017-08-07 14:59 ` Rik van Riel
[not found] ` <1502117991.6577.13.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-09 9:59 ` Kirill A. Shutemov
2017-08-09 12:31 ` Rik van Riel
2017-08-09 12:42 ` Florian Weimer [this message]
2017-08-10 13:05 ` Michal Hocko
[not found] ` <20170810130531.GS23863-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-10 13:23 ` Colm MacCárthaigh
[not found] ` <CAAF6GDc2hsj-XJj=Rx2ZF6Sh3Ke6nKewABXfqQxQjfDd5QN7Ug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-10 15:36 ` Michal Hocko
2017-08-10 16:17 ` Colm MacCárthaigh
[not found] ` <CAAF6GDeno6RpHf1KORVSxUL7M-CQfbWFFdyKK8LAWd_6PcJ55Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-10 17:01 ` Michal Hocko
[not found] ` <20170810170144.GA987-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-10 22:09 ` Colm MacCárthaigh
[not found] ` <CAAF6GDdFjS612mx1TXzaVk1J-Afz9wsAywTEijO2TG4idxabiw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 14:06 ` Michal Hocko
[not found] ` <20170811140653.GO30811-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-11 14:11 ` Florian Weimer
[not found] ` <c8cda773-b28d-f35f-7f18-6735584cb173-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-11 14:24 ` Michal Hocko
[not found] ` <20170811142457.GP30811-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2017-08-11 15:24 ` Florian Weimer
2017-08-11 15:31 ` Michal Hocko
2017-08-07 15:55 ` Colm MacCárthaigh
2017-08-07 16:02 ` Colm MacCárthaigh
2017-08-10 13:21 ` Michal Hocko
2017-08-10 14:11 ` Michal Hocko
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=8fe8040c-7595-ec09-6ce7-0da4fadc82c4@redhat.com \
--to=fweimer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=colm@allcosts.net \
--cc=dave.hansen@intel.com \
--cc=keescook@chromium.org \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=wad@chromium.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).