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

Date:   Mon, 14 Nov 2022 11:34:26 -0400
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Alex Williamson <alex.williamson@...hat.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        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 Mon, Nov 14, 2022 at 08:32:07AM -0700, Alex Williamson wrote:
> On Mon, 14 Nov 2022 09:35:39 -0400
> Jason Gunthorpe <jgg@...dia.com> wrote:
> 
> > 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
> 
> My plan is to merge back my fixes branch after it gets pulled into
> v6.1-rc so the vfio-iommufd support can be re-based to avoid this for
> v6.2.  Thanks,

It is fine, I will just merge v6.1 release into iommufd as-is, at the
end of the cycle, as I often do to fixup these rc conflicts.

At this point, due to all the testing, I don't really want to rebase
iommufd any further if I can avoid it.

Jason