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: <5C4C569E8A4B9B42A84A977CF070A35B2DA7A7F226@USINDEVS01.corp.hds.com>
Date:	Wed, 18 Jan 2012 17:40:30 -0500
From:	Seiji Aguchi <seiji.aguchi@....com>
To:	Kees Cook <keescook@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	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

>>>  static int __exit ramoops_remove(struct platform_device *pdev)
>>>  {
>>> +#if 0
>>> +     /* TODO(kees): We cannot unload ramoops since pstore doesn't support
>>> +      * unregistering yet.
>>> +      */
>>
>> Well that sucks.  Is pstore getting fixed?
>
>Tony, any plans for changing this? I'm ready when it does! :)
>
>

I have an question about this.

Are there any specific usecases you need to unload ramoops?

If users really would like to get kernel messages, unregistering ramoops is not needed.

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/