From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Hugh Dickins" <hugh@veritas.com>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Alan Jenkins" <alan-jenkins@tuffmail.co.uk>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Yinghai Lu" <yhlu.kernel@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Dave Jones" <davej@redhat.com>
Subject: Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption
Date: Sat, 6 Sep 2008 20:09:50 +0200 [thread overview]
Message-ID: <20080906180950.GA18649@elte.hu> (raw)
In-Reply-To: <48C06989.6080307@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > I would prefer you both to use the minimal memmap= solutions for
> > now; but others may disagree.
>
> The fact that we're seeing this problem in two completely different
> systems with different BIOSes and everything else makes me worried
> that this is quite widespread. It's only the persistence and
> diligence of our bug reporters that we managed to work out that
> they're the same problem. How many other people are getting strange
> crashes and haven't managed to correlate it any particular BIOS
> interaction? Or just happen to be corrupting memory we don't care
> about right now, but is only a small code change or link order change
> away from disaster?
please put this all behind a .config debug option that distros can turn
on/off. Also, when it's enabled in the .config, there should be another
.config option that marks it disabled by default but it can be enabled
via a boot parameter.
Distro debug kernels will most likely enable the .config - even release
kernels might enable it it, with default off - users can enable the boot
switch if they suspect something, without having to build a new kernel.
Ingo
next prev parent reply other threads:[~2008-09-06 18:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:52 [PATCH RFC] x86: check for and defend against BIOS memory corruption Jeremy Fitzhardinge
2008-08-29 1:49 ` Yinghai Lu
2008-08-29 3:28 ` Jeremy Fitzhardinge
2008-08-29 9:25 ` Alan Cox
2008-08-29 10:13 ` Rafał Miłecki
2008-08-29 10:06 ` Alan Cox
2008-08-29 10:24 ` Hugh Dickins
2008-08-29 11:54 ` Rafał Miłecki
2008-08-29 12:09 ` Alan Jenkins
2008-08-29 13:21 ` Hugh Dickins
2008-08-29 16:30 ` Rafał Miłecki
2008-08-29 17:39 ` Rafał Miłecki
2008-09-04 19:42 ` Rafał Miłecki
2008-09-04 20:23 ` Hugh Dickins
2008-09-04 23:04 ` Jeremy Fitzhardinge
2008-09-06 18:09 ` Ingo Molnar [this message]
2008-08-29 14:08 ` Jeremy Fitzhardinge
2008-08-29 14:18 ` Jeremy Fitzhardinge
2008-08-29 20:31 ` Kasper Sandberg
2008-08-30 1:15 ` Jeremy Fitzhardinge
2008-08-29 6:20 ` Rafał Miłecki
2008-08-29 6:45 ` Ingo Molnar
2008-08-29 7:21 ` Jeremy Fitzhardinge
2008-08-29 7:30 ` Ingo Molnar
2008-08-29 8:02 ` Jeremy Fitzhardinge
2008-08-29 7:22 ` Jeremy Fitzhardinge
2008-08-29 8:14 ` Hugh Dickins
2008-08-29 14:48 ` Jeremy Fitzhardinge
2008-08-29 17:20 ` H. Peter Anvin
2008-09-08 11:35 ` Hugh Dickins
2008-09-08 17:16 ` Jeremy Fitzhardinge
2008-09-08 19:14 ` Hugh Dickins
2008-09-08 19:45 ` Jeremy Fitzhardinge
2008-08-29 17:02 ` H. Peter Anvin
2008-08-29 17:03 ` H. Peter Anvin
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=20080906180950.GA18649@elte.hu \
--to=mingo@elte.hu \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
--cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).