From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V"
Date: Fri, 19 Apr 2024 12:44:36 +0200 [thread overview]
Message-ID: <2024041927-remedial-choking-c548@gregkh> (raw)
In-Reply-To: <20240416085647.14376-1-xingmingzheng@iscas.ac.cn>
On Tue, Apr 16, 2024 at 04:56:47PM +0800, Mingzheng Xing wrote:
> This reverts commit 1d6cd2146c2b58bc91266db1d5d6a5f9632e14c0 which has been
> merged into the mainline commit 39365395046f ("riscv: kdump: use generic
> interface to simplify crashkernel reservation"), but the latter's series of
> patches are not included in the 6.6 branch.
>
> This will result in the loss of Crash kernel data in /proc/iomem, and kdump
> loading the kernel will also cause an error:
>
> ```
> Memory for crashkernel is not reserved
> Please reserve memory by passing"crashkernel=Y@X" parameter to kernel
> Then try to loading kdump kernel
> ```
>
> After revert this patch, verify that it works properly on QEMU riscv.
>
> Link: https://lore.kernel.org/linux-riscv/ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv
> Signed-off-by: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
> ---
I do not understand, what branch is this for? Why have you not cc:ed
any of the original developers here? Why does Linus's tree not have the
same problem? And the first sentence above does not make much sense as
a 6.6 change is merged into 6.7?
confused,
greg k-h
next prev parent reply other threads:[~2024-04-19 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 8:56 [PATCH] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V" Mingzheng Xing
2024-04-19 10:44 ` Greg Kroah-Hartman [this message]
2024-04-19 12:26 ` Mingzheng Xing
2024-04-19 13:58 ` Greg Kroah-Hartman
2024-04-19 14:55 ` Mingzheng Xing
2024-04-23 13:12 ` Greg Kroah-Hartman
2024-04-24 3:40 ` Mingzheng Xing
2024-04-29 10:52 ` Greg Kroah-Hartman
2024-04-30 0:02 ` Baoquan He
2024-04-30 3:42 ` Mingzheng Xing
2024-04-24 1:06 ` Baoquan He
2024-04-24 5:18 ` Mingzheng Xing
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=2024041927-remedial-choking-c548@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=xingmingzheng@iscas.ac.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox