linux-kernel - Re: [PATCH v2] crash: use macro to add crashk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 26 Mar 2024 07:35:16 +0800
From: Baoquan He <bhe@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: kexec@...ts.infradead.org, mingo@...nel.org,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	chenhuacai@...ngson.cn, dyoung@...hat.com, jbohac@...e.cz,
	lihuafei1@...wei.com, chenhaixiang3@...wei.com
Subject: Re: [PATCH v2] crash: use macro to add crashk_res into iomem early
 for specific arch

On 03/25/24 at 01:29pm, Andrew Morton wrote:
> On Mon, 25 Mar 2024 09:50:50 +0800 Baoquan He <bhe@...hat.com> wrote:
> 
> > There are regression reports[1][2] that crashkernel region on x86_64 can't
> > be added into iomem tree sometime. This causes the later failure of kdump
> > loading.
> 
> So I think a cc:stable is needed.

Yeah, I forgot this.

> 
> > This happened after commit 4a693ce65b18 ("kdump: defer the insertion of
> > crashkernel resources") was merged.
> > 
> > Even though, these reported issues are proved to be related to other
> > component, they are just exposed after above commmit applied, I still
> > would like to keep crashk_res and crashk_low_res being added into iomem
> > early as before because the early adding has been always there on x86_64
> > and working very well. For safety of kdump, Let's change it back.
> 
> I'll use 4a693ce65b18 as the Fixes: target, since there is no
> "Exposed-by-non-buggy-patch:" tag.  To tell the -stable tree
> maintainers how far back in history this should be backported.

Thanks a lot.