linux-kernel - linux-next: manual merge of the iommufd tree with the vfio 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20251201124340.335d7144@canb.auug.org.au>
Date: Mon, 1 Dec 2025 12:43:40 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Jason Gunthorpe <jgg@...dia.com>, Alex Williamson <alex@...zbot.org>
Cc: Ankit Agrawal <ankita@...dia.com>, Jason Gunthorpe <jgg@...pe.ca>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the iommufd tree with the vfio tree

Hi all,

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

  include/linux/vfio_pci_core.h

between commit:

  9b92bc7554b5 ("vfio: refactor vfio_pci_mmap_huge_fault function")

from the vfio tree and commit:

  96ce2aeb15bd ("vfio/pci: Add vfio_pci_dma_buf_iommufd_map()")

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/vfio_pci_core.h
index 336a0e58b443,6a3074f2cf1c..000000000000
--- a/include/linux/vfio_pci_core.h
+++ b/include/linux/vfio_pci_core.h
@@@ -29,12 -28,8 +29,13 @@@ struct vfio_pci_core_device
  struct vfio_pci_region;
  struct p2pdma_provider;
  struct dma_buf_phys_vec;
+ struct dma_buf_attachment;
  
 +struct vfio_pci_eventfd {
 +	struct eventfd_ctx	*ctx;
 +	struct rcu_head		rcu;
 +};
 +
  struct vfio_pci_regops {
  	ssize_t (*rw)(struct vfio_pci_core_device *vdev, char __user *buf,
  		      size_t count, loff_t *ppos, bool iswrite);
@@@ -216,14 -204,7 +217,17 @@@ VFIO_IOREAD_DECLARATION(32
  VFIO_IOREAD_DECLARATION(64)
  #endif
  
 +static inline bool is_aligned_for_order(struct vm_area_struct *vma,
 +					unsigned long addr,
 +					unsigned long pfn,
 +					unsigned int order)
 +{
 +	return !(order && (addr < vma->vm_start ||
 +			   addr + (PAGE_SIZE << order) > vma->vm_end ||
 +			   !IS_ALIGNED(pfn, 1 << order)));
 +}
 +
+ int vfio_pci_dma_buf_iommufd_map(struct dma_buf_attachment *attachment,
+ 				 struct dma_buf_phys_vec *phys);
+ 
  #endif /* VFIO_PCI_CORE_H */

Content of type "application/pgp-signature" skipped