linux-kernel - Re: [Resend][Patch v2] kexec: increase max of kexec segments and use dynamic allocation

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]

Message-ID: <20100813104806.GA6077@hmsreliant.think-freely.org>
Date:	Fri, 13 Aug 2010 06:48:06 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Amerigo Wang <amwang@...hat.com>
Cc:	linux-kernel@...r.kernel.org, nhorman@...hat.com,
	kexec@...ts.infradead.org,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>, akpm@...ux-foundation.org,
	Vivek Goyal <vgoyal@...hat.com>,
	huang ying <huang.ying.caritas@...il.com>,
	ebiederm@...ssion.com
Subject: Re: [Resend][Patch v2] kexec: increase max of kexec segments and use
 dynamic allocation

On Fri, Aug 13, 2010 at 01:38:54AM -0400, Amerigo Wang wrote:
> 
> Currently KEXEC_SEGMENT_MAX is only 16 which is too small for machine with
> many memory ranges.  When hibernate on a machine with disjoint memory we do
> need one segment for each memory region. Increase this hard limit to 16K
> which is reasonably large.
> 
> And change ->segment from a static array to a dynamically allocated memory.
> 
> Cc: Neil Horman <nhorman@...hat.com>
> Cc: Vivek Goyal <vgoyal@...hat.com>
> Cc: huang ying <huang.ying.caritas@...il.com>
> Cc: Eric W. Biederman <ebiederm@...ssion.com>
> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>
> Cc: Paul Mackerras <paulus@...ba.org>
> Signed-off-by: WANG Cong <amwang@...hat.com>
> 
Concur with Simon

Reviewed-by: Neil Horman <nhorman@...driver.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/