[PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop bug at high
Baoquan He
bhe at redhat.com
Thu Jul 18 07:42:42 PDT 2024
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.
More information about the kexec
mailing list