linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
	hughd@google.com, aaron.lu@intel.com, akpm@linux-foundation.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: thp: remove use_zero_page sysfs knob
Date: Mon, 23 Jul 2018 13:31:08 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1807231329080.105582@chino.kir.corp.google.com> (raw)
In-Reply-To: <3118b646-681e-a2aa-dc7b-71d4821fa50f@linux.alibaba.com>

On Fri, 20 Jul 2018, Yang Shi wrote:

> I agree to keep it for a while to let that security bug cool down, however, if
> there is no user anymore, it sounds pointless to still keep a dead knob.
> 

It's not a dead knob.  We use it, and for reasons other than 
CVE-2017-1000405.  To mitigate the cost of constantly compacting memory to 
allocate it after it has been freed due to memry pressure, we can either 
continue to disable it, allow it to be persistently available, or use a 
new value for use_zero_page to specify it should be persistently 
available.

  reply	other threads:[~2018-07-23 20:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 18:13 Yang Shi
2018-07-20 19:32 ` Andrew Morton
2018-07-20 20:02   ` David Rientjes
2018-07-20 20:37     ` Yang Shi
2018-07-20 21:05       ` David Rientjes
2018-07-20 23:49         ` Yang Shi
2018-07-22  3:51         ` Matthew Wilcox
2018-07-23 20:28           ` David Rientjes
2018-07-23 21:33             ` David Rientjes
2018-07-23 21:49               ` Yang Shi
2018-07-24  9:08               ` Kirill A. Shutemov
2018-07-24 20:32                 ` David Rientjes
2018-07-20 21:06 ` Kirill A. Shutemov
2018-07-20 23:51   ` Yang Shi
2018-07-23 20:31     ` David Rientjes [this message]
2018-07-23 21:52       ` Yang Shi
2018-07-23 23:14         ` David Rientjes

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=alpine.DEB.2.21.1807231329080.105582@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=aaron.lu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yang.shi@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox