linux-kernel - Re: [PATCH] perf: fix kernel panic when parsing user space CS saved in pt

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: <20140605132118.GJ6758@twins.programming.kicks-ass.net>
Date:	Thu, 5 Jun 2014 15:21:18 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Cc:	Liu ShuoX <shuox.liu@...el.com>, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
	Zhang Yanmin <yanmin.zhang@...el.com>
Subject: Re: [PATCH] perf: fix kernel panic when parsing user space CS saved
 in pt_regs

On Thu, Jun 05, 2014 at 09:15:36PM +0800, Zhang, Yanmin wrote:

> Sorry for misleading you. It depends on backend. Pstore can use RAM or
> other storage, for example, EFI-provided backend. If using EFI backend,
> pstore can keep persistent across cold reset or even power outrages.
> 
> If using RAM, usually pstore can keep persistent at WarmReset. Since RAM
> access (even at non-cache mode) is fast and more flexible, in fact, we often use
> RAM as backend of pstore.

Funny definition of persistent you end up with in that case... :-) But
yes, that does explain.

Content of type "application/pgp-signature" skipped