From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
vgoyal@redhat.com, dyoung@redhat.com, arnd@arndb.de, afd@ti.com,
linus.walleij@linaro.org, akpm@linux-foundation.org,
eric.devolder@oracle.com, gregkh@linuxfoundation.org,
javierm@redhat.com, deller@gmx.de, robh@kernel.org,
hbathini@linux.ibm.com, thunder.leizhen@huawei.com,
chenjiahao16@huawei.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop bug at high
Date: Thu, 18 Jul 2024 22:42:42 +0800 [thread overview]
Message-ID: <Zpkp4iF7quCOq7k0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <aca0795c-f1a8-20c1-3daf-7f39d2ebf1bc@huawei.com>
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.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
vgoyal@redhat.com, dyoung@redhat.com, arnd@arndb.de, afd@ti.com,
linus.walleij@linaro.org, akpm@linux-foundation.org,
eric.devolder@oracle.com, gregkh@linuxfoundation.org,
javierm@redhat.com, deller@gmx.de, robh@kernel.org,
hbathini@linux.ibm.com, thunder.leizhen@huawei.com,
chenjiahao16@huawei.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop bug at high
Date: Thu, 18 Jul 2024 22:42:42 +0800 [thread overview]
Message-ID: <Zpkp4iF7quCOq7k0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <aca0795c-f1a8-20c1-3daf-7f39d2ebf1bc@huawei.com>
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.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: linux@armlinux.org.uk, catalin.marinas@arm.com, will@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
vgoyal@redhat.com, dyoung@redhat.com, arnd@arndb.de, afd@ti.com,
linus.walleij@linaro.org, akpm@linux-foundation.org,
eric.devolder@oracle.com, gregkh@linuxfoundation.org,
javierm@redhat.com, deller@gmx.de, robh@kernel.org,
hbathini@linux.ibm.com, thunder.leizhen@huawei.com,
chenjiahao16@huawei.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop bug at high
Date: Thu, 18 Jul 2024 22:42:42 +0800 [thread overview]
Message-ID: <Zpkp4iF7quCOq7k0@MiWiFi-R3L-srv> (raw)
In-Reply-To: <aca0795c-f1a8-20c1-3daf-7f39d2ebf1bc@huawei.com>
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.
next prev parent reply other threads:[~2024-07-18 14:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 3:54 [PATCH v3 0/3] crash: Fix x86_32 memory reserve dead loop bug Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 3:54 ` [PATCH v3 1/3] crash: Fix x86_32 crash " Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 11:10 ` Baoquan He
2024-07-18 11:10 ` Baoquan He
2024-07-18 11:10 ` Baoquan He
2024-07-18 12:11 ` Jinjie Ruan
2024-07-18 12:11 ` Jinjie Ruan
2024-07-18 12:11 ` Jinjie Ruan
2024-07-18 13:18 ` Jinjie Ruan
2024-07-18 13:18 ` Jinjie Ruan
2024-07-18 13:18 ` Jinjie Ruan
2024-07-18 3:54 ` [PATCH v3 2/3] crash: Fix x86_32 crash memory reserve dead loop bug at high Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 11:14 ` Baoquan He
2024-07-18 11:14 ` Baoquan He
2024-07-18 11:14 ` Baoquan He
2024-07-18 12:10 ` Jinjie Ruan
2024-07-18 12:10 ` Jinjie Ruan
2024-07-18 12:10 ` Jinjie Ruan
2024-07-18 14:42 ` Baoquan He [this message]
2024-07-18 14:42 ` Baoquan He
2024-07-18 14:42 ` Baoquan He
2024-07-18 3:54 ` [PATCH v3 3/3] ARM: Use generic interface to simplify crashkernel reservation Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-07-18 3:54 ` Jinjie Ruan
2024-08-05 7:51 ` Linus Walleij
2024-08-05 7:51 ` Linus Walleij
2024-08-05 7:51 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zpkp4iF7quCOq7k0@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenjiahao16@huawei.com \
--cc=dave.hansen@linux.intel.com \
--cc=deller@gmx.de \
--cc=dyoung@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=javierm@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.