public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch] Memory Error Handling Improvement
Date: Fri, 24 Jun 2005 21:36:18 +0000	[thread overview]
Message-ID: <17084.31954.385948.362059@napali.hpl.hp.com> (raw)
In-Reply-To: <200506231730.j5NHUNa96698484@clink.americas.sgi.com>

>>>>> On Fri, 24 Jun 2005 14:31:28 -0700, "Luck, Tony" <tony.luck@Intel.com> said:

  >> Fine, but what about my suggestion of just presuming that the access
  >> came for user-level unless you can prove otherwise?

  Tony> If the presumption is wrong, then you'll kill an innocent user process.

As opposed to panic'ing the kernel?  That doesn't strike me as a big
problem. ;-)

  Tony> Worse, you will let a corrupted kernel carry on running.

It'd boil down to the question of what the likelihood is that the
kernel would be touching a user-mapped page whose contents it depends
on for correct operation. (If it is not a user-mapped page, you'd
obviously _not_ conclude that the MCA was triggered by user-level.)

	--david

  parent reply	other threads:[~2005-06-24 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 17:30 [patch] Memory Error Handling Improvement Russ Anderson
2005-06-23 17:52 ` David Mosberger
2005-06-23 19:30 ` Russ Anderson
2005-06-23 22:11 ` Andreas Schwab
2005-06-23 22:18 ` David Mosberger
2005-06-23 22:22 ` Russ Anderson
2005-06-23 22:54 ` Andreas Schwab
2005-06-24  1:12 ` Hidetoshi Seto
2005-06-24 20:11 ` Russ Anderson
2005-06-24 20:18 ` Russ Anderson
2005-06-24 20:36 ` David Mosberger
2005-06-24 21:05 ` Luck, Tony
2005-06-24 21:11 ` David Mosberger
2005-06-24 21:20 ` Luck, Tony
2005-06-24 21:25 ` David Mosberger
2005-06-24 21:31 ` Luck, Tony
2005-06-24 21:36 ` Russ Anderson
2005-06-24 21:36 ` David Mosberger [this message]
2005-06-24 21:53 ` David Mosberger

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=17084.31954.385948.362059@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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