linux-kernel - Re: [PATCH] crash_core: Fix the check for whether crashkernel is from high memory

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20231209143418.92f02de6b6c6db2b7b3b1815@linux-foundation.org>
Date:   Sat, 9 Dec 2023 14:34:18 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Yuntao Wang <ytcoode@...il.com>
Cc:     linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
        Baoquan He <bhe@...hat.com>, Vivek Goyal <vgoyal@...hat.com>,
        Dave Young <dyoung@...hat.com>,
        Zhen Lei <thunder.leizhen@...wei.com>
Subject: Re: [PATCH] crash_core: Fix the check for whether crashkernel is
 from high memory

On Sat,  9 Dec 2023 22:14:38 +0800 Yuntao Wang <ytcoode@...il.com> wrote:

> If crash_base is equal to CRASH_ADDR_LOW_MAX, it also indicates that
> the crashkernel memory is allocated from high memory. However, the
> current check only considers the case where crash_base is greater than
> CRASH_ADDR_LOW_MAX. Fix it.
> 
> This patch also includes some minor cleanups.

Can we please include a description of the runtime effects of this
change?  ie, what happens now and under what circumstances, and how
does the fix alter these things?