linux-kernel - RE: [PATCH v5] ramoops: use pstore interface

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F01D107@ORSMSX104.amr.corp.intel.com>
Date:	Wed, 18 Jan 2012 22:37:45 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Kees Cook <keescook@...omium.org>
CC:	Marco Stornelli <marco.stornelli@...il.com>,
	Arnd Bergmann <arnd@...db.de>,
	Greg Kroah-Hartman <greg@...ah.com>,
	Randy Dunlap <rdunlap@...otime.net>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v5] ramoops: use pstore interface

> > +	/* TODO(kees): We cannot unload ramoops since pstore doesn't support
> > +	 * unregistering yet.
> > +	 */
>
> Well that sucks.  Is pstore getting fixed?

While it might be useful for developers who have machines that
support multiple back-ends to load & unload - there really isn't
any credible end-user case for it - so it has a very low priority.
Perhaps zero (it would complicate the code for no useful purpose).

Even for development there's a lot of re-booting (after all, pstore
is really about saving the kernel log when the system crashes :-).

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