linux-kernel - vt-d/iommu: RMRR-declared ACPI device handling in current VT-d Driver

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>] [day] [month] [year] [list]

Date:   Thu, 13 Dec 2018 01:14:56 +0800
From:   raymond pang <raymondpangxd@...il.com>
To:     joro@...tes.org, dwmw2@...radead.org
Cc:     iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: vt-d/iommu: RMRR-declared ACPI device handling in current VT-d Driver

Dear Joerg & David,
I have a question about current VT-d driver. I found it can not handle
following case:
An RMRR-declared ACPI device (it's also declared by ANDD) cannot
work using current VT-d driver. its DMAs will be blocked by VT-d.
The reason is that current VT-d driver only tries to setup identity map
for devices in dmar_rmrr_unit->device[]. But it doesn't add
RMRR-declared ACPI device into dmar_rmrr_unit->device[]. It just
allocates memory space for this ACPI device in dmar_parse_one_rmrr().
Let's see RMRR-declared PCI device. VT-d driver allocates memory
space for it and then adds it into dmar_rmrr_unit->device[] via
dmar_iommu_notify_scope_dev().
If there is any mistake, please correct me. Thanks

BRs,
Raymond