linux-kernel - [PATCH 0/3] acpi: Eliminate misleading erst pstore console message

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]

Date:	Fri, 28 Jun 2013 16:14:08 -0400
From:	Lenny Szubowicz <lszubowi@...hat.com>
To:	tony.luck@...el.com, cbouatmailru@...il.com,
	matt.fleming@...el.com, linux-kernel@...r.kernel.org
Cc:	n.hamaguchi@...fujitsu.com, dzickus@...hat.com
Subject: [PATCH 0/3] acpi: Eliminate misleading erst pstore console message 

On systems that have a valid ACPI ERST table, if the pstore.backend kernel
parameter selects a specific facility other than erst, then during boot the
following console message is displayed:

    ERST: Could not register with persistent store

This message makes it seem that something has gone wrong. In fact the same
message is used when you want ERST to be used by pstore and some real error
precludes registration.

The primary purpose of this 3 patch set is to avoid displaying this console
error message when another facility is explicitly selected as the backend for
pstore. Details are in the individual patches.


Lenny Szubowicz (3):
  pstore: Return unique error if backend registration excluded by kernel
    param
  acpi: Eliminate console msg if pstore.backend excludes ERST
  efivars: If pstore_register fails, free unneeded pstore buffer

 drivers/acpi/apei/erst.c          | 20 ++++++++++++++------
 drivers/firmware/efi/efi-pstore.c |  6 +++++-
 fs/pstore/platform.c              | 11 ++++++-----
 3 files changed, 25 insertions(+), 12 deletions(-)

-- 
1.8.2.1

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