linux-kernel - Re: [RFC PATCH 0/4 V2] introduce: livedump

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: <20120604210912.GA18354@redhat.com>
Date:	Mon, 4 Jun 2012 17:09:12 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	YOSHIDA Masanori <masanori.yoshida.tv@...achi.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Andy Lutomirski <luto@....edu>,
	Ingo Molnar <mingo@...e.hu>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Kees Cook <keescook@...omium.org>,
	Kevin Hilman <khilman@...com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Prarit Bhargava <prarit@...hat.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Tejun Heo <tj@...nel.org>,
	yrl.pp-manager.tt@...achi.com
Subject: Re: [RFC PATCH 0/4 V2] introduce: livedump

On Fri, May 25, 2012 at 06:12:07PM +0900, YOSHIDA Masanori wrote:

[..]
> (4) It allocates about 50% of physical RAM to store dumped pages. Currently
>     Live Dump saves all dumped data on memory once, and after that a user
>     becomes able to use the dumped data. Live Dump itself has no feature to
>     save dumped data onto a disk or any other storage device.

People complain when kdump reserves 128M of memory when system crashes.
I am skeptical that reserving 50% of memory for livedumps is going to fly.

Thanks
Vivek
--
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/