mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Gavin Shan" <gshan@alcatel-lucent.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Tough Issue: kernel instruction corruption
Date: Sat, 5 Jul 2008 08:17:37 -0700	[thread overview]
Message-ID: <20080705081737.5bc17450@infradead.org> (raw)
In-Reply-To: <008101c8deaa$52cf19d0$01fca8c0@microsof60b8d6>

On Sat, 5 Jul 2008 22:20:46 +0800
"Gavin Shan" <gshan@alcatel-lucent.com> wrote:

> Hello, I'm faced a tough issue recently: instructions of kernel
> were corrupted. There has 2 PCI buses on my board and lots
> of PCI devices with DMA capabality involved. I'm suspecting
> the kernel instructions were corrupted by DMA operations driving
> by those PCI devices with DMA capabality. 
> 
> Anybody have tried to protect kernel instructions from this case
> or have any ideas to protect kernel text section?

if you have a modern Intel board, you can enable the IOMMU on it that
will protect the kernel text (well, all of memory) from rogue DMA.
PPC generally has similar capabilities, as do some IBM x86 chipsets.

Without an IOMMU it's basically impossible to protect against such DMA.

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-05 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 14:20 Gavin Shan
2008-07-05 15:17 ` Arjan van de Ven [this message]
2008-07-05 15:26   ` Gavin Shan
2008-07-07 15:48 ` Stefan Richter

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=20080705081737.5bc17450@infradead.org \
    --to=arjan@infradead.org \
    --cc=gshan@alcatel-lucent.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®