[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e18bac6a57a4a45260e7282a70173fa6226955bc.camel@web.de>
Date: Fri, 14 Jun 2024 10:37:48 +0200
From: Bert Karwatzki <spasswolf@....de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Liam R. Howlett" <Liam.Howlett@...cle.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: commit 1c29a32ce65f4cd0f1c causes Bad rss-counter state and
firefox-esr crash in linux-next-20240613
Am Donnerstag, dem 13.06.2024 um 17:03 -0700 schrieb Andrew Morton:
> Let's hope Linus doesn't read this. Why are we nuking the entire
> planet just because some counter went wonky?
It's not just the wonky counter, the error always comes with a segfault which
causes a firefox tab to crash, though I've not yet figured out how this is
related to the BUG message or commit 1c29a32ce.
[ 179.393488] [ T2278] show_signal_msg: 16 callbacks suppressed
[ 179.393492] [ T2278] Privileged Cont[2278]: segfault at 22cddf91d3a0 ip
000022cde1aad010 sp 00007ffc616851a8 error 7 likely on CPU 15 (core 7, socket 0)
[ 179.393504] [ T2278] Code: Unable to access opcode bytes at 0x22cde1aacfe6.
[ 179.498173] [ T2289] BUG: Bad rss-counter state mm:00000000d0a3f682
type:MM_ANONPAGES val:1885
Bert Karwatzki
Powered by blists - more mailing lists