[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e0014e8-e251-360c-ad82-334ad0f28303@gmail.com>
Date: Mon, 29 Nov 2021 00:54:20 +0800
From: Fusion Future <qydwhotmail@...il.com>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-mm <linux-mm@...ck.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Paul Turner <pjt@...gle.com>, weixugc@...gle.com,
Greg Thelen <gthelen@...gle.com>,
Ingo Molnar <mingo@...hat.com>,
Jonathan Corbet <corbet@....net>,
Will Deacon <will@...nel.org>, Mike Rapoport <rppt@...nel.org>,
Kees Cook <keescook@...omium.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>, masahiroy@...nel.org,
Sami Tolvanen <samitolvanen@...gle.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"maintainer:X86 ARCHITECTURE" <x86@...nel.org>,
frederic@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>
Subject: Re: [PATCH 2/3] mm: page table check
> So it could be when memory consumption is over a certain percent, the bug will be triggered.
Bisected and at the commit "[04ce8955fbe4d84376b92b875c42942489fcf3c5]
mm: page table check", the system still doesn't encounter any freezes.
So it's not this commit that introduces the bug. Sorry for bothering.
Powered by blists - more mailing lists