linux-kernel - linux-next: manual merge of the iommufd tree with the iommu tree

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

Message-ID: <20230816162128.58ef5475@canb.auug.org.au>
Date:   Wed, 16 Aug 2023 16:21:28 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Jason Gunthorpe <jgg@...dia.com>, Joerg Roedel <joro@...tes.org>
Cc:     Jason Gunthorpe <jgg@...pe.ca>, Joerg Roedel <jroedel@...e.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Yi Liu <yi.l.liu@...el.com>
Subject: linux-next: manual merge of the iommufd tree with the iommu tree

Hi all,

Today's linux-next merge of the iommufd tree got a conflict in:

  include/linux/iommu.h

between commit:

  2b4de976b360 ("iommu: Pass in the iommu_device to probe for in bus_iommu_probe()")

from the iommu tree and commit:

  c64805327b7d ("iommu: Move dev_iommu_ops() to private header")

from the iommufd tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc include/linux/iommu.h
index 411ce9b998dc,f2d6a3989713..000000000000
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@@ -460,19 -459,7 +469,8 @@@ static inline void iommu_iotlb_gather_i
  	};
  }
  
- static inline const struct iommu_ops *dev_iommu_ops(struct device *dev)
- {
- 	/*
- 	 * Assume that valid ops must be installed if iommu_probe_device()
- 	 * has succeeded. The device ops are essentially for internal use
- 	 * within the IOMMU subsystem itself, so we should be able to trust
- 	 * ourselves not to misuse the helper.
- 	 */
- 	return dev->iommu->iommu_dev->ops;
- }
- 
 -extern int bus_iommu_probe(const struct bus_type *bus);
 +extern int bus_iommu_probe(const struct bus_type *bus,
 +			   struct iommu_device *iommu);
  extern bool iommu_present(const struct bus_type *bus);
  extern bool device_iommu_capable(struct device *dev, enum iommu_cap cap);
  extern bool iommu_group_has_isolated_msi(struct iommu_group *group);

Content of type "application/pgp-signature" skipped