linux-kernel - [PATCH 0/3] kdump: crashkernel parameter improvement

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

Message-Id: <20171024053147.493545734@redhat.com>
Date:   Tue, 24 Oct 2017 13:31:47 +0800
From:   dyoung@...hat.com
To:     kexec@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:     akpm@...ux-foundation.org, bhe@...hat.com, vgoyal@...hat.com,
        yinghai@...nel.org, corbet@....net, dyoung@...hat.com
Subject: [PATCH 0/3] kdump: crashkernel parameter improvement

Hi,

Here is a try to improve current crashkernel kernel parameter

Patch 1/3 adds an extra functionality so that one can use like
crashkernel=2G-:128M^12 to reserve 128M for 2G+ machine but also scale the
size based on system memory, that means 128M + (total_mem - 128M) >> 12

Patch 2/3 is a resending of previous post to let crashkernel=xM to reserve
first from below 896M, then <4G, then <MAXMEM

Patch 3/3 round up total system memory size because according to test the
mem size from memblock api is usually smaller than actual size, this passed
my tests on x86/arm/powerpc, it should work for most cases, but there might 
be exceptions, appreciated for any better idea.

Thanks
Dave