linux-kernel - linux-next: manual merge of the vfio tree with the s390 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]

Date:   Mon, 25 Jul 2022 16:33:56 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Alex Williamson <alex.williamson@...hat.com>
Cc:     Alexander Gordeev <agordeev@...ux.ibm.com>,
        Jason Gunthorpe <jgg@...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>,
        Tony Krowiak <akrowiak@...ux.ibm.com>
Subject: linux-next: manual merge of the vfio tree with the s390 tree

Hi all,

FIXME: Add owner of second tree to To:
       Add author(s)/SOB of conflicting commits.

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

  drivers/s390/crypto/vfio_ap_private.h

between commit:

  49b0109fb399 ("s390/vfio-ap: introduce shadow APCB")

from the s390 tree and commit:

  ce4b4657ff18 ("vfio: Replace the DMA unmapping notifier with a callback")

from the vfio 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 drivers/s390/crypto/vfio_ap_private.h
index 2d03871597bf,abb59d59f81b..000000000000
--- a/drivers/s390/crypto/vfio_ap_private.h
+++ b/drivers/s390/crypto/vfio_ap_private.h
@@@ -97,9 -81,6 +97,7 @@@ struct ap_queue_table 
   * @node:	allows the ap_matrix_mdev struct to be added to a list
   * @matrix:	the adapters, usage domains and control domains assigned to the
   *		mediated matrix device.
 + * @shadow_apcb:    the shadow copy of the APCB field of the KVM guest's CRYCB
-  * @iommu_notifier: notifier block used for specifying callback function for
-  *		    handling the VFIO_IOMMU_NOTIFY_DMA_UNMAP even
   * @kvm:	the struct holding guest's state
   * @pqap_hook:	the function pointer to the interception handler for the
   *		PQAP(AQIC) instruction.
@@@ -114,8 -90,6 +112,7 @@@ struct ap_matrix_mdev 
  	struct vfio_device vdev;
  	struct list_head node;
  	struct ap_matrix matrix;
 +	struct ap_matrix shadow_apcb;
- 	struct notifier_block iommu_notifier;
  	struct kvm *kvm;
  	crypto_hook pqap_hook;
  	struct mdev_device *mdev;

Content of type "application/pgp-signature" skipped