| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100404085338.GU24846@8bytes.org> Date: Sun, 4 Apr 2010 10:53:38 +0200 From: Joerg Roedel <joro@...tes.org> To: Bernhard Walle <bernhard@...lle.de> Cc: "Eric W. Biederman" <ebiederm@...ssion.com>, nhorman@...hat.com, nhorman@...driver.com, Joerg Roedel <joerg.roedel@....com>, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org, Chris Wright <chrisw@...s-sol.org>, hbabu@...ibm.com, iommu@...ts.linux-foundation.org, vgoyal@...hat.com Subject: Re: [PATCH 3/4] Revert "x86: disable IOMMUs on kernel crash" On Sun, Apr 04, 2010 at 09:24:30AM +0200, Bernhard Walle wrote: > Am 03.04.10 19:49, schrieb Eric W. Biederman: > > Not a problem. We require a lot of things of the kdump kernel, > > and it is immediately apparent in a basic sanity test. > > Also, in most cases (for example: distribution kernels), the kdump > kernel nowadays is identical to the running kernel. So, if the running > kernel has IOMMU support, the kdump kernel also has. Yes, I know. But is that a requirement for kexec? If not we still potentially have this problem. It is a smaller problem than data-corruption caused by in-flight dma because most people^Wdistributions indeed use the same kernel for normal boot and kexec, thats true. Joerg -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists