public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gavin Shan" <gshan@alcatel-lucent.com>
To: <linux-kernel@vger.kernel.org>
Subject: Tough Issue: kernel instruction corruption
Date: Sat, 5 Jul 2008 22:20:46 +0800	[thread overview]
Message-ID: <008101c8deaa$52cf19d0$01fca8c0@microsof60b8d6> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 592 bytes --]

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?

Thanks in advance,
Gavinÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

             reply	other threads:[~2008-07-05 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 14:20 Gavin Shan [this message]
2008-07-05 15:17 ` Tough Issue: kernel instruction corruption Arjan van de Ven
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='008101c8deaa$52cf19d0$01fca8c0@microsof60b8d6' \
    --to=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