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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 20 Feb 2023 16:09:01 +0100
From:   Hans Verkuil <hverkuil@...all.nl>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        Linux Media Mailing List <linux-media@...r.kernel.org>
Cc:     Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        nicolas@...fresne.ca, xavier.claessens@...labora.com,
        benjamin.gaignard@...labora.com
Subject: Re: v4l2-test-controls.cpp(325): expected 8 private controls, got 7

On 20/02/2023 15:42, Naresh Kamboju wrote:
> Following v4l2 tests are failing on Linux mainline v6.2 on arm64 hikey device.
> Am I missing anything in my test environment ?
> 
> Driver Info:
> ----------
>   Driver name      : vivid
>   Bus info         : platform:vivid-000
>   Driver version   : 6.2.0
> 
> Fail  log:
> ---------
>     fail: v4l2-test-controls.cpp(325): expected 8 private controls, got 7
>   test VIDIOC_QUERY_EXT_CTRL/QUERYMENU: FAIL
>     fail: v4l2-test-controls.cpp(366): qctrl.step || qctrl.minimum ||
> qctrl.maximum || qctrl.default_value
>   test VIDIOC_QUERYCTRL: FAIL
> ..
>     fail: v4l2-test-controls.cpp(473): g_ctrl returned an error (22)
>   test VIDIOC_G/S_CTRL: FAIL
> ..
>     fail: v4l2-test-controls.cpp(593): returned control value out of range
>     fail: v4l2-test-controls.cpp(706): invalid control 0098f90f
>   test VIDIOC_G/S/TRY_EXT_CTRLS: FAIL
> ..
>     fail: v4l2-test-formats.cpp(264): fmtdesc.description mismatch:
> was 'Y/UV 4:2:0', expected 'Y/CbCr 4:2:0'

This suggests that you are running with an old(er) v4l-utils version, since I adapted
v4l2-compliance to avoid this failure. It's due to a change in the kernel, so currently
both old and new descriptions are accepted.

Looking at the logs:

v4l2-compliance SHA: 5d8c459c1bf9 2021-04-08 13:28:26

That's much too old.

Regards,

	Hans

>   test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL
> 
> 
> Test details,
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/tests/
> https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.2/testrun/14859062/suite/v4l2-compliance/test/VIDIOC_ENUM_FMT-FRAMESIZES-FRAMEINTERVALS/log
> 
> --
> Linaro LKFT
> https://lkft.linaro.org

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ