linux-kernel - RE: [PATCH] efi: Avoid sysfs spew on reboot and panic

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]

Date:	Fri, 23 Sep 2011 10:11:17 -0700
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Chen Gong <gong.chen@...ux.intel.com>,
	Matthew Garrett <mjg@...hat.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"mikew@...gle.com" <mikew@...gle.com>,
	"saguchi@...hat.com" <saguchi@...hat.com>
Subject: RE: [PATCH] efi: Avoid sysfs spew on reboot and panic

> If you insist on your design, I prefer deleting the function pstore_write before 
> applying your patch. We all know no real users to call this function,
> every backend will register Its own callback, so this function is useless at all.

We could do that. I threw in pstore_write without any particular use case in mind.
Since there hasn't been a rush of people adding calls to it (and since it seems
that pstore back ends have very limited amounts of space at their disposal, any
use of pstore_write would probably cause problems for the dmesg dump model)
removing it sounds like a good idea.

If someone does want to use it - they will have to figure out how to solve
priority issues.

-Tony