linux-kernel - Re: [PATCH v2 1/2] mm: Move page struct poisoning to CONFIG_DEBUG_VM_PAGE_INIT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0c1c36f7-f45a-8fe9-dd52-0f60b42064a9@intel.com>
Date:   Thu, 6 Sep 2018 07:59:03 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Michal Hocko <mhocko@...nel.org>,
        Alexander Duyck <alexander.duyck@...il.com>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        alexander.h.duyck@...el.com, pavel.tatashin@...rosoft.com,
        akpm@...ux-foundation.org, mingo@...nel.org,
        kirill.shutemov@...ux.intel.com
Subject: Re: [PATCH v2 1/2] mm: Move page struct poisoning to
 CONFIG_DEBUG_VM_PAGE_INIT_POISON

On 09/05/2018 10:47 PM, Michal Hocko wrote:
> why do you have to keep DEBUG_VM enabled for workloads where the boot
> time matters so much that few seconds matter?

There are a number of distributions that run with it enabled in the
default build.  Fedora, for one.  We've basically assumed for a while
that we have to live with it in production environments.

So, where does leave us?  I think we either need a _generic_ debug
option like:

	CONFIG_DEBUG_VM_SLOW_AS_HECK

under which we can put this an other really slow VM debugging.  Or, we
need some kind of boot-time parameter to trigger the extra checking
instead of a new CONFIG option.