[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5dc8ef6-587d-e286-af80-568094a65007@intel.com>
Date: Thu, 6 Sep 2018 10:07:51 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Pasha Tatashin <Pavel.Tatashin@...rosoft.com>,
Alexander Duyck <alexander.duyck@...il.com>,
"mhocko@...nel.org" <mhocko@...nel.org>
Cc: linux-mm <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
"Duyck, Alexander H" <alexander.h.duyck@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...nel.org>,
"Kirill A. Shutemov" <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/06/2018 09:12 AM, Pasha Tatashin wrote:
>
> I do not want to make this feature less tested. Poisoning memory allowed
> us to catch corner case bugs like these:
>
> ab1e8d8960b68f54af42b6484b5950bd13a4054b
> mm: don't allow deferred pages with NEED_PER_CPU_KM
>
> e181ae0c5db9544de9c53239eb22bc012ce75033
> mm: zero unavailable pages before memmap init
>
> And several more that were fixed by other people.
Just curious: were these found in the wild, or by a developer doing
normal development having turned on lots of debug options?
Powered by blists - more mailing lists