Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754856AbYGGPsj (ORCPT ); Mon, 7 Jul 2008 11:48:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753679AbYGGPsb (ORCPT ); Mon, 7 Jul 2008 11:48:31 -0400 Received: from hp3.statik.tu-cottbus.de ([141.43.120.68]:34634 "EHLO hp3.statik.tu-cottbus.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753445AbYGGPsa (ORCPT ); Mon, 7 Jul 2008 11:48:30 -0400 Message-ID: <48723ABB.4060009@s5r6.in-berlin.de> Date: Mon, 07 Jul 2008 17:48:11 +0200 From: Stefan Richter User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Gavin Shan CC: linux-kernel@vger.kernel.org Subject: Re: Tough Issue: kernel instruction corruption References: <008101c8deaa$52cf19d0$01fca8c0@microsof60b8d6> In-Reply-To: <008101c8deaa$52cf19d0$01fca8c0@microsof60b8d6> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 19 Gavin Shan wrote: > 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? IOMMU hardware can give some protection. Correctly working PCI devices and _correct drivers_ would be good to have too. -- Stefan Richter -=====-==--- -=== --=== http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/