[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e0e7d631-0af4-46fc-b606-78de07ebb88a@redhat.com>
Date: Thu, 21 Dec 2023 12:32:04 +0100
From: David Hildenbrand <david@...hat.com>
To: Oliver Sang <oliver.sang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Matthew Wilcox <willy@...radead.org>, oe-lkp@...ts.linux.dev,
lkp@...el.com, Linux Memory Management List <linux-mm@...ck.org>,
linux-kernel@...r.kernel.org
Subject: Re: [linux-next:master] [mm] bbcbf2a3f0: kernel_BUG_at_mm/memory.c
On 21.12.23 12:23, Oliver Sang wrote:
> hi, Andrew Morton,
>
> On Wed, Dec 20, 2023 at 02:11:35PM -0800, Andrew Morton wrote:
>> On Tue, 19 Dec 2023 23:46:50 +0800 kernel test robot <oliver.sang@...el.com> wrote:
>>
>>>
>>>
>>> Hello,
>>>
>>> kernel test robot noticed "kernel_BUG_at_mm/memory.c" on:
>>>
>>> commit: bbcbf2a3f05f74f9d268eab57abbdce6a65a94ad ("mm: convert ksm_might_need_to_copy() to work on folios")
>>
>> I assume this is a bisection result, so it's quite repeatable?
>
> yes, we bisect to this commit, it's quite repeatable:
>
> ddd06bb63d9793ce bbcbf2a3f05f74f9d268eab57ab
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 100% 6:6 dmesg.Kernel_panic-not_syncing:Fatal_exception
> :6 100% 6:6 dmesg.RIP:do_swap_page
> :6 100% 6:6 dmesg.invalid_opcode:#[##]
> :6 100% 6:6 dmesg.kernel_BUG_at_mm/memory.c
>
>
Can you try with the snipped I sent? Please let me know if you need a
full patch for testing purposes.
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists