From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Pekka Enberg" <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip] kmemcheck: fix crash in PnP BIOS calls
Date: Sun, 5 Oct 2008 20:10:56 +0100 [thread overview]
Message-ID: <20081005201056.5b9b2f53@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <19f34abd0810051204u241659b4j6a9ef2ab3616d3fc@mail.gmail.com>
> catch those reads/writes just fine. I'm not sure if the BIOS code can
> change segments (it would need to switch LDT/GDTs, I think), and even
It can do so if it wants as far as I can tell
> if it did, I find it unlikely that it would directly access kernel
> memory using these new segment registers. Do you happen to know of any
> such cases?
No. The code either seems to be very simple or just be an SMM trap in the
BIOSes I've seen
prev parent reply other threads:[~2008-10-05 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 17:25 Vegard Nossum
2008-10-05 18:15 ` Alan Cox
2008-10-05 19:04 ` Vegard Nossum
2008-10-05 19:10 ` Alan Cox [this message]
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=20081005201056.5b9b2f53@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=vegard.nossum@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
all inboxes | Powered by JetHome®