[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiZ7WJQ1y=CwuMwqBxQYtaD8psq+Vxa3r1Z6_ftDZK+hA@mail.gmail.com>
Date: Mon, 5 Aug 2024 19:40:07 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Guenter Roeck <linux@...ck-us.net>, Vlastimil Babka <vbabka@...e.cz>
Cc: linux-kernel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH 6.10 000/809] 6.10.3-rc3 review
[ Let's drop random people and bring in Vlastimil ]
Vlastimil,
it turns out that the "this patch" is entirely a red herring, and the
problem comes and goes randomly with just some code layout issues. See
http://server.roeck-us.net/qemu/parisc64-6.10.3/
for more detail, particularly you'll see the "log.bad.gz" with the full log.
See also
https://lore.kernel.org/all/87y15a4p4h.ffs@tglx/
for this thread.
I don't think this is really a slub issue, since it only happens on
parisc, but maybe you can see what would make parisc different, and
what could possibly make it all timing- or layout-dependent.
Linus
On Sun, 4 Aug 2024 at 11:36, Guenter Roeck <linux@...ck-us.net> wrote:
>
> With this patch in v6.10.3, all my parisc64 qemu tests get stuck with repeated error messages
>
> [ 0.000000] =============================================================================
> [ 0.000000] BUG kmem_cache_node (Not tainted): objects 21 > max 16
> [ 0.000000] -----------------------------------------------------------------------------
>
> This never stops until the emulation aborts.
Powered by blists - more mailing lists