linux-kernel - [PATCH v2 0/6] Merge ramoops and persistent

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

Message-ID: <20120516124109.GA14658@lizard>
Date:	Wed, 16 May 2012 05:41:09 -0700
From:	Anton Vorontsov <anton.vorontsov@...aro.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Kees Cook <keescook@...omium.org>,
	Colin Cross <ccross@...roid.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	John Stultz <john.stultz@...aro.org>,
	Shuah Khan <shuahkhan@...il.com>, arve@...roid.com,
	Rebecca Schultz Zavin <rebecca@...roid.com>,
	Jesper Juhl <jj@...osbits.net>,
	Randy Dunlap <rdunlap@...otime.net>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Thomas Meyer <thomas@...3r.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Marco Stornelli <marco.stornelli@...il.com>,
	WANG Cong <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	linaro-kernel@...ts.linaro.org, patches@...aro.org,
	kernel-team@...roid.com
Subject: [PATCH v2 0/6] Merge ramoops and persistent_ram, generic pstore RAM
 backend

Hi all,

Here is v2 of the previous patch set. The series do not include
patches that were already merged.

I believe I addressed all the previous comments, plus now the
series include another small cleanup patch.

Here's some background for the series:

There are currently two competing debug facilities to store kernel
messages in a persistent storage: a generic pstore and Google's
persistent_ram. Not so long ago (https://lkml.org/lkml/2012/3/8/252),
it was decided that we should fix this situation.

Recently ramoops has switched to pstore, which basically means that
it became a RAM backend for the pstore framework.

persistent_ram+ram_console and ramoops+pstore have almost the same
features, except:

1. Ramoops doesn't support ECC. Having ECC is useful when a hardware
   reset was used to bring the machine back to life (i.e. a watchdog
   triggered). In such cases, RAM may be somewhat corrupt, but
   usually it is restorable.

2. Pstore doesn't support logging kernel messages in run-time, it only
   dumps dmesg when kernel oopses/panics. This makes pstore useless for
   debugging hangs caused by HW issues or improper use of HW (e.g.
   weird device inserted -> driver tried to write a reserved bits ->
   SoC hanged. In that case we don't get any messages in the pstore.

These patches solve the first issue, plus move things to their
proper places. Patches that will fix the second issue will be sent
shortly.

--- 
 Documentation/ramoops.txt                |    8 +-
 drivers/char/Kconfig                     |    9 -
 drivers/char/Makefile                    |    1 -
 drivers/char/ramoops.c                   |  362 --------------------
 drivers/staging/android/Kconfig          |   10 +-
 drivers/staging/android/Makefile         |    1 -
 drivers/staging/android/persistent_ram.c |  530 -----------------------------
 drivers/staging/android/persistent_ram.h |   84 -----
 drivers/staging/android/ram_console.c    |    2 +-
 fs/pstore/Kconfig                        |   17 +
 fs/pstore/Makefile                       |    3 +
 fs/pstore/ram.c                          |  383 +++++++++++++++++++++
 fs/pstore/ram_core.c                     |  532 ++++++++++++++++++++++++++++++
 include/linux/pstore_ram.h               |   98 ++++++
 include/linux/ramoops.h                  |   17 -
 15 files changed, 1042 insertions(+), 1015 deletions(-)

-- 
Anton Vorontsov
Email: cbouatmailru@...il.com
--
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/