Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: AMD boot woe due to "x86/mm: Cleanup pgprot_4k_2_large() and pgprot_large_2_4k()"
Date:   Wed, 22 Apr 2020 12:35:08 -0400
Message-Id: <59604C7F-696A-45A3-BF4F-C8913E09DD4C@lca.pw>
References: <20200422161757.GC26846@zn.tnic>
Cc:     Christoph Hellwig <hch@lst.de>,
        "Peter Zijlstra (Intel)" <peterz@infradead.org>,
        x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
        kasan-dev <kasan-dev@googlegroups.com>
In-Reply-To: <20200422161757.GC26846@zn.tnic>
To:     Borislav Petkov <bp@alien8.de>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Apr 22, 2020, at 12:18 PM, Borislav Petkov <bp@alien8.de> wrote:
>=20
> What is the special thing about this config? You have KASAN enabled and?
> Anything else?
>=20
> I need to know what are the relevant switches you've enabled so that I
> can enable them on my box too and try to reproduce.

The config has a few extra memory debugging options enabled like KASAN, debu=
g_pagealloc, debug_vm etc. The affected machines are NUMA AMD servers.=