Files
kernel_arpi/include/uapi/linux
Hans Verkuil cc7d2dfb75 [media] v4l2_plane_pix_format: use __u32 bytesperline instead of __u16
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>
2015-04-02 23:54:47 -03:00
..
2014-10-20 10:30:15 +08:00
2014-09-23 23:15:46 -07:00
2015-02-02 18:09:42 +01:00
2014-10-14 13:08:29 +11:00
2014-07-01 10:48:05 -06:00
2014-03-20 14:55:18 +01:00
2014-11-19 14:48:02 -06:00
2014-12-08 12:55:57 +08:00
2014-08-08 15:57:31 -07:00
2014-05-14 10:04:34 +01:00
2014-12-16 11:19:42 -05:00
2014-12-22 16:12:36 -05:00
2015-01-05 22:44:46 -05:00
2014-12-02 13:52:53 -07:00
2015-02-17 14:34:51 -08:00
2014-08-08 15:57:31 -07:00
2014-03-04 13:51:06 -05:00
2015-01-20 13:51:06 +01:00
2014-12-13 12:42:52 -08:00
2015-02-02 18:46:51 -08:00
2014-03-21 14:21:13 -04:00
2015-01-21 19:21:30 +01:00
2015-02-07 18:43:16 +08:00
2014-12-10 17:41:10 -08:00
2014-12-09 14:10:41 +08:00
2014-04-26 12:13:24 -04:00
2015-02-10 12:38:14 -07:00
2014-12-09 12:06:31 +02:00
2014-12-09 12:05:24 +02:00