[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zpkp4iF7quCOq7k0@MiWiFi-R3L-srv>
Date: Thu, 18 Jul 2024 22:42:42 +0800
From: Baoquan He <bhe@...hat.com>
To: Jinjie Ruan <ruanjinjie@...wei.com>
Cc: linux@...linux.org.uk, catalin.marinas@....com, will@...nel.org,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com, vgoyal@...hat.com,
dyoung@...hat.com, arnd@...db.de, afd@...com,
linus.walleij@...aro.org, akpm@...ux-foundation.org,
eric.devolder@...cle.com, gregkh@...uxfoundation.org,
javierm@...hat.com, deller@....de, robh@...nel.org,
hbathini@...ux.ibm.com, thunder.leizhen@...wei.com,
chenjiahao16@...wei.com, linux-kernel@...r.kernel.org,
kexec@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop
bug at high
On 07/18/24 at 08:10pm, Jinjie Ruan wrote:
>
>
> On 2024/7/18 19:14, Baoquan He wrote:
> > On 07/18/24 at 11:54am, Jinjie Ruan wrote:
> >
> > I don't fully catch the subject, what does the 'dead loop bug at high'
> > mean?
>
> It means alloc at [CRASH_ADDR_LOW_MAX, CRASH_ADDR_HIGH_MAX] repeatedly
> which corresponds to the crashkernel parameter of the "high".
That may mislead people to think it's a crashkernel=,high setting and
the corresponding issue.
Maybe "crash: Fix x86_32 crashkernel reservation dead loop" is good
enough.
Powered by blists - more mailing lists