mirror of
https://github.com/FEX-Emu/linux.git
synced 2025-01-02 15:21:03 +00:00
cc7d2dfb75
While running v4l2-compliance tests on vivid I suddenly got errors due to a call to vmalloc_user with size 0 from vb2. Digging deeper into the cause I discovered that this was due to the fact that struct v4l2_plane_pix_format defines bytesperline as a __u16 instead of a __u32. The test I was running selected a format of 4 * 4096 by 4 * 2048 with a 32 bit pixelformat. So bytesperline was 4 * 4 * 4096 = 65536, which becomes 0 in a __u16. And bytesperline * height is suddenly 0 as well. While the vivid driver may be a virtual driver, it is to be expected that this limit will be hit for real hardware as well in the near future: 8k deep-color video will already reach it. The solution is to change the type to __u32. The only drivers besides vivid that use the multiplanar API are little-endian ARM and SH platforms (exynos, ti-vpe, vsp1), so this is safe. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com> |
||
---|---|---|
.. | ||
media | ||
.gitignore | ||
80211.tmpl | ||
alsa-driver-api.tmpl | ||
crypto-API.tmpl | ||
debugobjects.tmpl | ||
device-drivers.tmpl | ||
deviceiobook.tmpl | ||
drm.tmpl | ||
filesystems.tmpl | ||
gadget.tmpl | ||
genericirq.tmpl | ||
kernel-api.tmpl | ||
kernel-hacking.tmpl | ||
kernel-locking.tmpl | ||
kgdb.tmpl | ||
libata.tmpl | ||
librs.tmpl | ||
lsm.tmpl | ||
Makefile | ||
media_api.tmpl | ||
mtdnand.tmpl | ||
networking.tmpl | ||
rapidio.tmpl | ||
regulator.tmpl | ||
s390-drivers.tmpl | ||
scsi.tmpl | ||
sh.tmpl | ||
stylesheet.xsl | ||
tracepoint.tmpl | ||
uio-howto.tmpl | ||
usb.tmpl | ||
w1.tmpl | ||
writing_musb_glue_layer.tmpl | ||
writing_usb_driver.tmpl | ||
writing-an-alsa-driver.tmpl | ||
z8530book.tmpl |