[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120723141322.GA23047@srcf.ucam.org>
Date: Mon, 23 Jul 2012 15:13:22 +0100
From: Matthew Garrett <mjg@...hat.com>
To: Seiji Aguchi <seiji.aguchi@....com>
Cc: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Luck, Tony (tony.luck@...el.com)" <tony.luck@...el.com>,
"mikew@...gle.com" <mikew@...gle.com>,
"dzickus@...hat.com" <dzickus@...hat.com>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: Re: [RFC][PATCH v2 0/3] efi_pstore: avoid losing critical message
On Thu, Jul 19, 2012 at 09:11:44PM +0000, Seiji Aguchi wrote:
> [Patch Descriptions]
> Patch 1/3 and 2/3 take fist approach, _not_ overwriting entries.
>
> Patch 3/3 takes second approach, adding some logic overwriting entries.
>
> 1/3: Avoid overwriting existing entry
> This patch just avoid overwriting entries to save the 1st critical message
> without being influenced by subsequent events.
I think there's a good argument in favour of this approach. Userspace
crash report tools should be taught to copy the crash data and then
remove the existing entries. It avoids any of the complexity associated
with other approaches and ensures that behaviour is always consistent.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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/
Powered by blists - more mailing lists