linux-kernel - Re: [Patch] 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]

Date:	Tue, 27 Jul 2010 16:14:14 +0800
From:	Cong Wang <amwang@...hat.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
CC:	huang ying <huang.ying.caritas@...il.com>,
	linux-kernel@...r.kernel.org, nhorman@...hat.com,
	akpm@...ux-foundation.org
Subject: Re: [Patch] kexec: increase max of kexec segments and use dynamic
 allocation

On 07/26/10 20:19, Eric W. Biederman wrote:
> Cong Wang<amwang@...hat.com>  writes:
>
>> So, what is a better number? 2048? :)
>
> I was thinking something a little ridiculous like 10K or 64K.
>
> Assuming the usage you care about is something like hibernate on a
> machine with disjoint memory where you truly need one segment for
> each memory region.
>
> The only point of a limit at all once we introduce dynamic allocation
> is to catch buggy apps.
>

Ok, I will change that number and improve the changelog.

Thanks.


-- 
The opposite of love is not hate, it's indifference.
  - Elie Wiesel
--
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/