[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fccbe6b1bd533a84f50cd675b57ecb17@linux.dev>
Date: Wed, 09 Nov 2022 11:48:58 +0000
From: "Yajun Deng" <yajun.deng@...ux.dev>
To: "Mike Rapoport" <rppt@...ux.ibm.com>
Cc: "Sachin Sant" <sachinp@...ux.ibm.com>,
"linuxppc-dev" <linuxppc-dev@...ts.ozlabs.org>,
"open list" <linux-kernel@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: [6.1.0-rc3-next-20221104] Boot failure - kernel BUG at
mm/memblock.c:519
November 9, 2022 7:42 PM, "Mike Rapoport" <rppt@...ux.ibm.com> wrote:
> Hi Yajun,
>
> On Wed, Nov 09, 2022 at 11:32:27AM +0000, Yajun Deng wrote:
>
>> November 9, 2022 6:55 PM, "Sachin Sant" <sachinp@...ux.ibm.com> wrote:
>>
>> On 09-Nov-2022, at 3:55 PM, Yajun Deng <yajun.deng@...ux.dev> wrote:
>>
>> November 9, 2022 6:03 PM, "Yajun Deng" <yajun.deng@...ux.dev> wrote:
>>
>> Hey Mike,
>>
>> Sorry, this email should be sent to Sachin but not Mike.
>> Please forgive my confusion. So:
>>
>> Hey Sachin,
>> Can you help me test the attached file?
>> Please use this new patch instead of the one in memblock tree.
>>
>> Thanks for the fix. With the updated patch kernel boots correctly.
>>
>> Thanks for your test results.
>>
>> Hi Mike,
>> Do you have any other suggestions for this patch? If not, I'll send a v3 patch.
>
> Unfortunately I don't think the new version has much value as it does not
> really eliminate the second loop in case memory allocation is required.
> I'd say the improvement is not worth the churn.
>
OK, I got it.
>> Tested-by: Sachin Sant <sachinp@...ux.ibm.com <sachinp@...ux.ibm.com>>
>>
>> - Sachin
>
> --
> Sincerely yours,
> Mike.
Powered by blists - more mailing lists