[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABXGCsN7LBynNk_XzaFm2eVkryVQ26BSzFkrxC2Zb5GEwTvc1g@mail.gmail.com>
Date: Thu, 9 May 2024 16:59:30 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: David Hildenbrand <david@...hat.com>
Cc: Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: 6.9/BUG: Bad page state in process kswapd0 pfn:d6e840
On Wed, May 8, 2024 at 10:45 PM David Hildenbrand <david@...hat.com> wrote:
>
> "page dumped because: non-NULL mapping"
>
> Is the relevant bit. We are freeing a page, but page->mapping is not
> NULL. IIUC, it might happen under memory pressure when reclaiming memory.
>
> It's weird that only you are seeing that, if it would be something
> "obvious" I would expect multiple reports :/
>
Maybe because the problem is really difficult to reproduce (rare
combination of the kernel build option and workload). I even thought
that the problem was fixed because it did not reproduce itself for a
week.
But yesterday when it happened again with the kworker process, I
stopped doubting that it was fixed.
Now I am concerned with the question of how to be as useful as
possible when reproducing bug again?
--
Best Regards,
Mike Gavrilov.
Powered by blists - more mailing lists