linux-kernel - RFC: IOMMU/AMD: Error Handling

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Apr 2013 14:45:30 -0500
From:	Suravee Suthikulanit <suravee.suthikulpanit@....com>
To:	Jörg Rödel <joro@...tes.org>,
	"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RFC: IOMMU/AMD: Error Handling

Joerg,

We are in the process of implementing AMD IOMMU error handling, and I 
would like some comments from you and the community.

Currently, the AMD IOMMU driver only reports events from the event log 
in the dmesg, and does not try to handle them in case of errors.  AMD 
IOMMU errors can be categorized as device-specific errors and IOMMU errors.

1. For IOMMU errors such as:
     - DEV_TAB_HADWARE_ERROR
     - PAGE_TAB_ERROR
     - COMMAND_HARDWARE_ERROR
If the error is detected during IOMMU initialization, we could disable 
IOMMU and proceed.  If the error occurs after IOMMU is initialized, we 
won't be able to recover from this, and might need to result in panic.

2. For device-specific errors such as:
     - ILLEGAL_DEV_TABLE_ENTRY
     - IO_PAGE_FAULT
     - INVALDE_DEVICE_REQUEST
We think the AMD IOMMU driver should try to isolate the device. This 
involves blocking device transactions at IOMMU DTE and tries to disable 
the device (e.g. calling the remove(struct pci_dev *pdev) interface 
generally provides by device drivers).  This could prevents the device 
from continuing to fail and to risk of system instability.

3. In case of posted memory write transaction, device driver might not 
be aware that the transaction has failed and blocked at IOMMU. If there 
is no HW IOMMU, I believe this is handled by PCI error handling code.  
If the IOMMU hardware reporth such case, could this potentially leverage 
the Linux IOMMU fault handling interface, iommu_set_fault_handler() and 
report_iommu_fault(),  to communicate to device driver or PCI driver?

Any feedback or comments are appreciated.

Thank you,
Suravee

--
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/