diff options
| author | Jonas Karlman <[email protected]> | 2022-05-13 22:29:14 +0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2022-05-17 10:06:31 +0200 |
| commit | 77e74be83083194f949f4979a35dec9012348d3b (patch) | |
| tree | b8c156c53dee7d7e8c9dd64ae849de3b5ab64c5b /lib/test_fortify/write_overflow-memcpy.c | |
| parent | cf76bb4d5e74ac4211f1fa47052b30fa7dd6443f (diff) | |
media: rkvdec: h264: Validate and use pic width and height in mbs
The width and height in macroblocks is currently configured based on OUTPUT
buffer resolution, this works for frame pictures but can cause issues for
field pictures.
When frame_mbs_only_flag is 0 the height in mbs should be height of
the field instead of height of frame.
Validate pic_width_in_mbs_minus1 and pic_height_in_map_units_minus1
against OUTPUT buffer resolution and use these values to configure HW.
The validation is happening in both try_ctrt() and start() since it is
otherwise possible to trick the driver during initialization by changing
the OUTPUT format after having set a valid control.
[hverkuil: when -> When (first word in a comment block)]
Signed-off-by: Jonas Karlman <[email protected]>
Signed-off-by: Nicolas Dufresne <[email protected]>
Reviewed-by: Ezequiel Garcia <[email protected]>
Signed-off-by: Hans Verkuil <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions