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
| ||
|
Date: Wed, 27 Jun 2018 09:55:48 +0800 From: Alex Williamson <alex.williamson@...hat.com> To: Gerd Hoffmann <kraxel@...hat.com> Cc: airlied@...ux.ie, dri-devel@...ts.freedesktop.org, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, christian.koenig@....com, daniel.vetter@...ll.ch, Kirti Wankhede <kwankhede@...dia.com>, "open list:VFIO MEDIATED DEVICE DRIVERS" <kvm@...r.kernel.org> Subject: Re: [PATCH 2/2] sample/mdev/mbochs: add mbochs_kunmap_dmabuf On Tue, 26 Jun 2018 09:32:33 +0200 Gerd Hoffmann <kraxel@...hat.com> wrote: > > > .map = mbochs_kmap_dmabuf, > > > + .unmap = mbochs_kunmap_dmabuf, > > > .mmap = mbochs_mmap_dmabuf, > > > }; > > > > > > > Is this a fix for v4.18? > > Yes. > > > AFAICT, the kmap_atomic removal is only in > > next, not yet upstream and hopefully includes this sample driver before > > hitting mainline. Should we therefore have a v4.18-rc based patch for > > this to include before v4.18 to resolve this? > > The kmap_atomic interface will be removed in 4.19 because nobody uses > it, so dropping the mbochs implementation already in 4.18 should not > cause any issues. > > So just queue both for 4.18 would be the easiest way do deal with the > dependency I think. Ok, so I'll drop the fixes tag and apply both to my for-linus branch for v4.18 and then Christian won't need to include it for the v4.19 patch. Thanks, Alex
Powered by blists - more mailing lists