[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211118135234.0905b6ad@gandalf.local.home>
Date: Thu, 18 Nov 2021 13:52:34 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Gavin Shan <gshan@...hat.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
LKML <linux-kernel@...r.kernel.org>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Gerald Schaefer <gerald.schaefer@...ux.ibm.com>,
"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [BUG] WARNING: CPU: 3 PID: 1 at mm/debug_vm_pgtable.c:493
On Thu, 18 Nov 2021 10:33:39 -0800
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> Gavin, Anshuman? Feel free to tell me what I missed.
Let me know if you would like me to add more debugging. The failure happens
once every few weeks or so.
>
> Otherwise, we should disable those PUD tests (or fix them, of course).
>
> For now, I consider this WARN_ON() to be a failure of the testing
> infrastructure, not of the VM code.
For now, I'm just going to comment out those WARN_ON()s in my tests, as it
causes me to have to restart them :-p (I can modify the testing scripts to
restart where it last failed as it is a couple of hours into the tests when
it triggers, but it is still a pain).
-- Steve
Powered by blists - more mailing lists