linux-kernel - Re: df36ac1bc2a16 ("pstore: Don't allow high traffic options on fragile devices")

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: <20140410185724.GC4704@pd.tnic>
Date:	Thu, 10 Apr 2014 20:57:24 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	Matt Fleming <matt@...sole-pimps.org>,
	linux-efi <linux-efi@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: df36ac1bc2a16 ("pstore: Don't allow high traffic options on
 fragile devices")

On Thu, Apr 10, 2014 at 06:34:34PM +0000, Luck, Tony wrote:
> Speed is also a factor ... waiting for flash to update for each
> printk() would mess up timing so much that you might not see the
> problem you are chasing.

Gaah, there's that too. I guess nvram access speeds slower than in the
msec range (I'm looking at my printk timestamps) are no good for us.

> A better EFI trick for this would be "capsules". They live in regular
> RAM and BIOS firmware does stuff with them at warm reset time. Matt
> has been looking at them - but BIOS support for them seems sketchy to
> none right now.

Hmm, I'm wondering whether we could put a bunch of sanity checks into
fwts to run on a box and check needed capsules functionality before
logging to one.

Matt, looks like we have ourselves a new project. :-)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/