linux-kernel - Re: [PATCH] media: v4l: marvell: select CONFIG_V4L2

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] [thread-next>] [day] [month] [year] [list]

Date: Wed, 14 Feb 2024 11:58:07 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Hans Verkuil" <hverkuil-cisco@...all.nl>,
 "Sakari Ailus" <sakari.ailus@...ux.intel.com>
Cc: "Arnd Bergmann" <arnd@...nel.org>, linux-media@...r.kernel.org,
 linux-kernel@...r.kernel.org, "Mauro Carvalho Chehab" <mchehab@...nel.org>
Subject: Re: [PATCH] media: v4l: marvell: select CONFIG_V4L2_ASYNC where needed

On Wed, Feb 14, 2024, at 11:54, Hans Verkuil wrote:
> On 14/02/2024 11:48, Arnd Bergmann wrote:
>
>> It was definitely working before ff3cc65cadb5 ("media: v4l: async,
>> fwnode: Improve module organisation") in linux-5.13, but it's not
>> clear if that is the culprit. It's probably safe to backport
>> to v5.15 and higher.
>
>
> If it has been broken for so long, then should we bother with v6.8?
>
> I'm not saying we should, I just like to get your opinion on this.

I don't have a strong opinion either way, there is very little
risk and very little benefit in backporting.

If we apply it to 6.8 at all, I think it should also be in
v5.15+ LTS and vice versa, but only queuing it for 6.9 is
fine with me, too.

     Arnd