From: Matthew Garrett <mjg@redhat.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mikew@google.com" <mikew@google.com>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>,
"dzickus@redhat.com" <dzickus@redhat.com>
Subject: Re: [RFC][PATCH v2 2/3] Hold multiple logs
Date: Tue, 24 Jul 2012 22:07:25 +0100 [thread overview]
Message-ID: <20120724210725.GA29109@srcf.ucam.org> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F19370D21@ORSMSX104.amr.corp.intel.com>
On Tue, Jul 24, 2012 at 08:54:59PM +0000, Luck, Tony wrote:
> Now we panic. Pstore asks EFI "Do you have any space?" EFI replies "No". Pstore can't even overwrite
> one of the old OOPs records ... because it thinks they have all been erased. So we lose the panic
> log.
I think we inevitably lose in that scenario. I'd need to verify, but my
recollection is that overwriting existing variables may be equivalent to
a delete/create cycle.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-07-24 21:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 21:13 [RFC][PATCH v2 2/3] Hold multiple logs Seiji Aguchi
2012-07-19 21:22 ` Luck, Tony
2012-07-19 21:43 ` Seiji Aguchi
2012-07-19 22:10 ` Luck, Tony
2012-07-19 23:08 ` Seiji Aguchi
2012-07-19 23:42 ` Luck, Tony
2012-07-20 0:39 ` Seiji Aguchi
2012-07-20 3:03 ` Don Zickus
2012-07-20 13:24 ` Seiji Aguchi
2012-07-20 13:42 ` Seiji Aguchi
2012-07-20 14:29 ` Don Zickus
2012-07-20 16:56 ` Luck, Tony
2012-07-20 18:49 ` Seiji Aguchi
2012-07-23 14:16 ` Matthew Garrett
2012-07-24 17:23 ` Seiji Aguchi
2012-07-24 17:52 ` Luck, Tony
2012-07-24 18:18 ` Matthew Garrett
2012-07-24 19:57 ` Luck, Tony
2012-07-24 20:39 ` Seiji Aguchi
2012-07-24 20:54 ` Luck, Tony
2012-07-24 21:07 ` Matthew Garrett [this message]
2012-07-24 21:12 ` Luck, Tony
2012-07-24 21:26 ` Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120724210725.GA29109@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=dzickus@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.