| 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
| ||
|
Date: Tue, 30 Sep 2014 13:02:01 +0200 From: Joerg Roedel <joro@...tes.org> To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, David Woodhouse <dwmw2@...radead.org>, Jiang Liu <jiang.liu@...ux.intel.com> Cc: iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org, joro@...tes.org, jroedel@...e.de Subject: [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind Hi, here is a patch-set to fix an issue recently discovered when the Intel IOMMU is in use with devices that need RMRR mappings. The problem is that the RMRR mappings are destroyed when the device driver is unbound from the device, causing DMAR faults. To solve this problem a device driver core change is necessary to catch the right point in time for the IOMMU code to destroy any mappings for a device. With this patch-set the RMRR mappings are only destroyed when the device is actually removed from the system. Please review. Thanks, Joerg Joerg Roedel (2): driver core: Add BUS_NOTIFY_REMOVED_DEVICE event iommu/vt-d: Only remove domain when device is removed drivers/base/core.c | 3 +++ drivers/iommu/intel-iommu.c | 11 +---------- include/linux/device.h | 11 ++++++----- 3 files changed, 10 insertions(+), 15 deletions(-) -- 1.9.1 -- 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