linux-kernel - Re: [PATCH] platform/chrome: Add pstore platform

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: <CAOesGMhPYq4i9j3iTSPvi5iAB5rEBxmdFdj57QsKLPeOVg+Pyg@mail.gmail.com>
Date:	Mon, 25 Nov 2013 12:49:34 -0800
From:	Olof Johansson <olof@...om.net>
To:	Randy Dunlap <rdunlap@...radead.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kees Cook <keescook@...omium.org>,
	Benson Leung <bleung@...omium.org>
Subject: Re: [PATCH] platform/chrome: Add pstore platform_device

On Mon, Nov 25, 2013 at 12:04 PM, Randy Dunlap <rdunlap@...radead.org> wrote:
> On 11/25/13 11:37, Olof Johansson wrote:
>> Add the ramoops pstore device so that we get logs of panics across reboots.
>>
>> Signed-off-by: Olof Johansson <olof@...om.net>
>> ---
>>
>>  drivers/platform/chrome/Kconfig           |  14 +++++
>>  drivers/platform/chrome/Makefile          |   1 +
>>  drivers/platform/chrome/chromeos_pstore.c | 101 ++++++++++++++++++++++++++++++
>>  3 files changed, 116 insertions(+)
>>  create mode 100644 drivers/platform/chrome/chromeos_pstore.c
>>
>> diff --git a/drivers/platform/chrome/Kconfig b/drivers/platform/chrome/Kconfig
>> index b13303e75a34..06c53c8132ad 100644
>> --- a/drivers/platform/chrome/Kconfig
>> +++ b/drivers/platform/chrome/Kconfig
>> @@ -25,4 +25,18 @@ config CHROMEOS_LAPTOP
>>         If you have a supported Chromebook, choose Y or M here.
>>         The module will be called chromeos_laptop.
>>
>> +config CHROMEOS_PSTORE
>> +     tristate "Chrome OS pstore support"
>> +     ---help---
>> +       This module instantiates the persistent storage on x86 ChromeOS
>> +       devices. It can be used to store away console logs and crash
>> +       information across reboots.
>> +
>> +       The range of memory used is 0xf00000-0x1000000, tradionally the
>
>                                                           traditionally

Thanks! Fixed in-tree but won't repost if this is the only feedback.


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