On Mon, Apr 6, 2020 at 3:16 PM Gerd Hoffmann kraxel@redhat.com wrote:
Hi,
+drivers/gpu/drm/virtio/virtgpu_object.c maintainers Now we have both mainline and linux-next boot broken (linux-next is broken for the past 40 days). No testing of new code happens.
virtio_gpu_object_shmem_init drivers/gpu/drm/virtio/virtgpu_object.c:151 [inline] virtio_gpu_object_create+0x9f3/0xaa0 drivers/gpu/drm/virtio/virtgpu_object.c:230
Ah, that one.
broken patch: f651c8b05542 ("drm/virtio: factor out the sg_table from virtio_gpu_object") fixed by: 0666a8d7f6a4 ("drm/virtio: fix OOB in virtio_gpu_object_create")
Both are in drm-misc-next. I suspect the fix was added after drm-misc-next was closed for the 5.7 merge window and thus should have been submitted to drm-misc-next-fixes instead.
So, what to do now? Should I cherry-pick 0666a8d7f6a4 into drm-misc-next-fixes? Or should it go into drm-misc-fixes instead?
Yup cherry-pick it over, with -x, to drm-misc-next-fixes. -Daniel
Done. So the next linux-next build should be green again.
Linux-next is boot broken with 2 or 3 other bugs for a month. This won't fix linux-next.