[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180108174653.7muglyihpngxp5tl@black.fi.intel.com>
Date: Mon, 8 Jan 2018 20:46:53 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Mike Galbraith <efault@....de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Borislav Petkov <bp@...e.de>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-mm@...ck.org
Subject: Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at
runtime for CONFIG_SPARSEMEM_EXTREME=y
On Mon, Jan 08, 2018 at 04:04:44PM +0000, Ingo Molnar wrote:
>
> hi Kirill,
>
> As Mike reported it below, your 5-level paging related upstream commit
> 83e3c48729d9 and all its followup fixes:
>
> 83e3c48729d9: mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y
> 629a359bdb0e: mm/sparsemem: Fix ARM64 boot crash when CONFIG_SPARSEMEM_EXTREME=y
> d09cfbbfa0f7: mm/sparse.c: wrong allocation for mem_section
>
> ... still breaks kexec - and that now regresses -stable as well.
>
> Given that 5-level paging now syntactically depends on having this commit, if we
> fully revert this then we'll have to disable 5-level paging as well.
Urghh.. Sorry about this.
I'm on vacation right now. Give me a day to sort this out.
--
Kirill A. Shutemov
Powered by blists - more mailing lists