linux-kernel - [PATCH 0/2] iommufd/selftest: Fix and cleanup for bus ops

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 for Android: free password hash cracker in your pocket

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

Message-Id: <cover.1701165201.git.robin.murphy@arm.com>
Date:   Tue, 28 Nov 2023 10:42:10 +0000
From:   Robin Murphy <robin.murphy@....com>
To:     joro@...tes.org, jgg@...pe.ca, kevin.tian@...el.com
Cc:     will@...nel.org, iommu@...ts.linux.dev,
        linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] iommufd/selftest: Fix and cleanup for bus ops

Hi all,

The bus ops removal relies on iommu_ops_from_fwnode(NULL) finding the
"global" hardware driver ops on relevant platforms. Unfortunately I
overlooked that this will also match the IOMMUFD mock driver, such that
it can end up claiming to be the IOMMU for real platform etc. devices
which don't have an IOMMU described by a fwspec. This mini-series
addresses that.

I've split it so patch #1 is  minimal fix that mitigates the issue and
could be applied independently, then patch #2 then builds on it to take
full advantage of the new machinery and coexist as a normal IOMMU
driver. However they could be squashed if preferred.

Thanks,
Robin.

Robin Murphy (2):
  iommufd/selftest: Use a fwnode to distinguish devices
  iommufd/selftest: Use normal IOMMU registration

 drivers/iommu/iommu-priv.h           |  7 -----
 drivers/iommu/iommu.c                | 46 +++-------------------------
 drivers/iommu/iommufd/iommufd_test.h |  2 ++
 drivers/iommu/iommufd/selftest.c     | 45 +++++++++++++--------------
 4 files changed, 27 insertions(+), 73 deletions(-)

-- 
2.39.2.101.g768bb238c484.dirty