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: <3908561D78D1C84285E8C5FCA982C28F170D020E@ORSMSX104.amr.corp.intel.com>
Date:	Mon, 9 Apr 2012 21:42:09 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Kees Cook <keescook@...omium.org>
CC:	"shuahkhan@...il.com" <shuahkhan@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Marco Stornelli <marco.stornelli@...il.com>
Subject: RE: [PATCH v5] ramoops: use pstore interface

> The patch breaks ramoops module unloading.  Tony says there's "no
> credible end-user case" for this and Marco promptly provided one,
> which was ignored.

I'm not sure that I understood Marco's use case. He said:

> First of all ramoops was born mainly for debug purpose and
> to help the maintainability of a product. I used it in systems
> where the uptime (so no reboot) was important. So it can be
> very useful for me load the module, gather logs and unload it
> for example. A kernel panic is not recoverable so the reboot
> is needed but it's not always true for a kernel oops.

In the non-crashed oops case ... aren't all the logs you need
in /var/log/messages?

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