linux-kernel - Re: [PATCH] mm,x86: initialize high mem before free_all

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20111206103618.GE15966@elte.hu>
Date:	Tue, 6 Dec 2011 11:36:18 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	linux-mm@...ck.org, x86@...nel.org, linux-kernel@...r.kernel.org,
	Mel Gorman <mgorman@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] mm,x86: initialize high mem before free_all_bootmem()


* Stanislaw Gruszka <sgruszka@...hat.com> wrote:

> On Tue, Dec 06, 2011 at 09:25:55AM +0100, Ingo Molnar wrote:
> > The thing is, the pagealloc bug you fixed basically kept 
> > pagealloc debugging essentially disabled for a really long time, 
> > correct?
> Yes, it worked only in special cases.
>  
> > So i'd expect there to be quite a few latent problems - 
> > i'll give it some more testing before pushing out the result.
>
> Ehh, I expect them too, but fortunately only with 
> CONFIG_DEBUG_PAGEALLOC, non-debug kernel are not affected.

I test DEBUG_PAGEALLOC=y kernels all the time - i just booted a 
32-bit and a 64-bit allyesconfig kernel an hour ago.

Miraculously everything appears to be in working order so far.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/