linux-kernel - RE: [PATCH v2 3/3] efi: Add support for using efivars as a pstore backend

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: <987664A83D2D224EAE907B061CE93D5301E70D902F@orsmsx505.amr.corp.intel.com>
Date:	Tue, 7 Jun 2011 14:35:56 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Matt_Domsch@...l.com" <Matt_Domsch@...l.com>
Subject: RE: [PATCH v2 3/3] efi: Add support for using efivars as a pstore
 backend

> Yeah. I guess the question then is whether the mediation should be in 
> pstore or at the platform backend level. strcmp in pstore_register seems 
> somehow fragile for this, but I guess it'd work?

I don't think it all that fragile.  All the back ends will have
unique names.  If the user doesn't specify a pstore= argument we
keep the current "first past the post" method. If they do, then they
can choose which one, or specify pstore=none (or even pstore=not-bloody-likely,
since any not matching string will disable) to turn it off altogether.

-Tony
--
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/