linux-kernel - Re: [GIT PULL] Linux Media vimc update for 6.20-rc1

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]

Message-ID: <d002bedd-6fa0-458b-87cb-24146ff58e17@linuxfoundation.org>
Date: Wed, 14 Jan 2026 08:54:38 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: Hans Verkuil <hverkuil+cisco@...nel.org>,
 Mauro Carvalho Chehab <mchehab@...nel.org>,
 Pavan Bobba <opensource206@...il.com>
Cc: Kieran Bingham <kieran.bingham@...asonboard.com>,
 Hans Verkuil <hverkuil@...all.nl>, linux-kernel@...r.kernel.org,
 linux-media@...r.kernel.org, shuah <shuah@...nel.org>,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [GIT PULL] Linux Media vimc update for 6.20-rc1

On 1/13/26 02:19, Hans Verkuil wrote:
> Hi Shuah, Pavan,
> 
> On 08/01/2026 22:42, Shuah Khan wrote:
>> Hi Mauro,
>>
>> Please pull the vimc next update for Linux 6.20-rc1.
>>
>> Adds
>>       RGB/YUV input entity implementation
>>       support for V4L2_FIELD_ALTERNATE in vimc-sensor
>>       support for multiple RGB formats in vimc-debayer
>>       support custom bytesperline values in vimc-capture
>>       document RGB/YUV input entity
>>
>> diff is attached.
> 
> Unfortunately these vimc changes cause regressions in the vimc test-media test.
> 
> This test is run in our CI to catch regressions, so it must always pass.
> 
> The test is in the v4l-utils git repository (https://git.linuxtv.org/v4l-utils.git/)
> in the contrib/test directory. It's run as: 'sudo ./test-media vimc'.
> 
> It could be that these changes require changes in the vimc test itself.
> In that case I need a patch for test-media fixing this. However, looking
> at the failures I think that at least some of the issues are caused by these
> patches.
> 
> Since this series adds a new entity, I think that test-media needs to be patched
> anyway with a new test that tests this new entity as well.

Thank you Hans.

Pavan, please address the problems in the patch series.


> 
> Running the test-media vimc test results in:
> 
> Summary:
> 
> Total for vimc device /dev/media4: 8, Succeeded: 8, Failed: 0, Warnings: 0
> Total for vimc device /dev/video13: 60, Succeeded: 49, Failed: 11, Warnings: 0
> Total for vimc device /dev/video14: 60, Succeeded: 60, Failed: 0, Warnings: 0
> Total for vimc device /dev/video15: 60, Succeeded: 49, Failed: 11, Warnings: 0
> Total for vimc device /dev/v4l-subdev0: 54, Succeeded: 54, Failed: 0, Warnings: 0
> Total for vimc device /dev/v4l-subdev1: 54, Succeeded: 54, Failed: 0, Warnings: 0
> Total for vimc device /dev/v4l-subdev2: 61, Succeeded: 59, Failed: 2, Warnings: 0
> Total for vimc device /dev/v4l-subdev3: 61, Succeeded: 59, Failed: 2, Warnings: 0
> Total for vimc device /dev/v4l-subdev4: 54, Succeeded: 52, Failed: 2, Warnings: 0
> Total for vimc device /dev/v4l-subdev5: 61, Succeeded: 61, Failed: 0, Warnings: 0
> Total for vimc device /dev/v4l-subdev6: 47, Succeeded: 47, Failed: 0, Warnings: 0
> Total for vimc device /dev/v4l-subdev7: 47, Succeeded: 47, Failed: 0, Warnings: 0
> Grand Total for vimc device /dev/media4: 627, Succeeded: 599, Failed: 28, Warnings: 0
> 
> So I'm dropping this PR.
> 

Makes sense.

thanks,
-- Shuah