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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5C4C569E8A4B9B42A84A977CF070A35B2DA7A7F237@USINDEVS01.corp.hds.com>
Date:	Wed, 18 Jan 2012 18:20:08 -0500
From:	Seiji Aguchi <seiji.aguchi@....com>
To:	Kees Cook <keescook@...omium.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Tony Luck <tony.luck@...el.com>,
	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

>> Are there any specific usecases you need to unload ramoops?
>
>For me, it would be useful during development. Beyond that, not that I can see.

Thank you for your quick relay. I understood this is useful for you.

But, as Tony said, I think this is a low priority because 
there is a side effect for end users.
If they unload ramoops by mistake, messages will be lost.

In my opinion, we have to consider whether each feature 
is truly needed for end users (not for developers).

Seiji

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