linux-kernel - Re: linux-next: manual merge of the iommufd tree with the vfio-fixes 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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y3JEK376qqpBcYAq@nvidia.com>
Date:   Mon, 14 Nov 2022 09:35:39 -0400
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Alex Williamson <alex.williamson@...hat.com>,
        Anthony DeRossi <ajderossi@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the iommufd tree with the vfio-fixes
 tree

On Fri, Nov 11, 2022 at 03:37:35PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the iommufd tree got a conflict in:
> 
>   drivers/vfio/vfio_main.c
> 
> between commit:
> 
>   7fdba0011157 ("vfio: Fix container device registration life cycle")
> 
> from the vfio-fixes tree and commit:
> 
>   55e16a188913 ("vfio: Move vfio_device driver open/close code to a function")
> 
> from the iommufd tree.
> 
> I fixed it up (I just used the latter version since it seems to
> incorporate the former change) and can carry the fix as necessary. 

Yes, that is right, it is as Alex and I discussed

Thanks
Jason