stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
Cc: Baoquan He <bhe@redhat.com>,
	stable@vger.kernel.org, Chen Jiahao <chenjiahao16@huawei.com>
Subject: Re: [PATCH v2] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V"
Date: Tue, 30 Apr 2024 09:54:46 +0200	[thread overview]
Message-ID: <2024043037-enroll-polygon-e7eb@gregkh> (raw)
In-Reply-To: <7f976727-3ad8-4071-9a91-4a32a01abd32@iscas.ac.cn>

On Tue, Apr 30, 2024 at 11:51:53AM +0800, Mingzheng Xing wrote:
> On 4/30/24 11:39, Baoquan He wrote:
> > On 04/30/24 at 11:24am, Mingzheng Xing wrote:
> >> This reverts commit 1d6cd2146c2b58bc91266db1d5d6a5f9632e14c0 which was
> >> mistakenly added into v6.6.y and the commit corresponding to the 'Fixes:'
> >> tag is invalid. For more information, see link [1].
> >>
> >> This will result in the loss of Crashkernel data in /proc/iomem, and kdump
> >> failed:
> >>
> >> ```
> >> 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, kdump works fine. Tested on QEMU riscv.
> >>
> >> Link: https://lore.kernel.org/linux-riscv/ZSiQRDGLZk7lpakE@MiWiFi-R3L-srv [1]
> >> Cc: Baoquan He <bhe@redhat.com>
> >> Cc: Chen Jiahao <chenjiahao16@huawei.com>
> >> Signed-off-by: Mingzheng Xing <xingmingzheng@iscas.ac.cn>
> > 
> > Ack. This is necessary for v6.6.y stable branch.
> > 
> > Acked-by: Baoquan He <bhe@redhat.com>
> > 
> 
> Thanks,
> 
> Hi, Greg. This is for the 6.6.y branch only.

Thanks, now queued up.

greg k-h

      reply	other threads:[~2024-04-30  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30  3:24 [PATCH v2] Revert "riscv: kdump: fix crashkernel reserving problem on RISC-V" Mingzheng Xing
2024-04-30  3:39 ` Baoquan He
2024-04-30  3:51   ` Mingzheng Xing
2024-04-30  7:54     ` Greg Kroah-Hartman [this message]

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=2024043037-enroll-polygon-e7eb@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bhe@redhat.com \
    --cc=chenjiahao16@huawei.com \
    --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;
as well as URLs for NNTP newsgroup(s).