| 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: <20100331212535.GR29241@sequoia.sous-sol.org> Date: Wed, 31 Mar 2010 14:25:35 -0700 From: Chris Wright <chrisw@...s-sol.org> To: Neil Horman <nhorman@...driver.com> Cc: iommu@...ts.linux-foundation.org, joerg.roedel@....com, vgoyal@...hat.com, hbabu@...ibm.com, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] amd iommu: force flush of iommu prior during shutdown * Neil Horman (nhorman@...driver.com) wrote: > Flush iommu during shutdown > > When using an iommu, its possible, if a kdump kernel boot follows a primary > kernel crash, that dma operations might still be in flight from the previous > kernel during the kdump kernel boot. This can lead to memory corruption, > crashes, and other erroneous behavior, specifically I've seen it manifest during > a kdump boot as endless iommu error log entries of the form: > AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.1 domain=0x000d > address=0x000000000245a0c0 flags=0x0070] We've already fixed this problem once before, so some code shift must have brought it back. Personally, I prefer to do this on the bringup path than the teardown path. Besides keeping the teardown path as simple as possible (goal is to get to kdump kernel asap), there's also reason to competely flush on startup in genernal in case BIOS has done anything unsavory. thanks, -chris -- 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