linux-kernel - Re: [RFD] pstore: pmsg: ramoops: add multiple pmsg instances

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] [day] [month] [year] [list]

Message-ID: <56244E8D.5040303@hitachi.com>
Date:	Mon, 19 Oct 2015 10:59:41 +0900
From:	Hiraku Toyooka <hiraku.toyooka.gu@...achi.com>
To:	Mark Salyzyn <salyzyn@...roid.com>, <tony.luck@...el.com>,
	<keescook@...omium.org>, <anton@...msg.org>, <ccross@...roid.com>,
	<seiji.aguchi.tr@...achi.com>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFD] pstore: pmsg: ramoops: add multiple pmsg instances

Hello Mark,

(I'm sorry for my late reply.)

Mark Salyzyn wrote:
>> I'm trying to make the feature of multiple pmsg instances for ramoops.
> I like it, in fact I encourage it.

Thank you.

> Multiple instances does allow one to control individual content aging or
> priority, I agree with your assessment, but make sure that you have a
> bona fide user for it (even if it is just for yourself)?

Yes. There are embedded devices which have limited NVRAM and no
HDD/SSD. Especially in our usage, the devices are industrial
machinery. When we catch a system failure, for fixing the root cause of
the failure, we often have to distinguish if it happend suddenly or if
there were signs long before the failure. Multiple pmsg can help this
kind of cause analysis with small NVRAM because higher priority
messages are preserved for a long time.

> NB: ToDo: device tree support for pstore configuration

Would you mean pstore backend's configuration (e.g.'mem_address' in
ramoops)?

Best regards,
Hiraku Toyooka

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