linux-kernel - Re: [PATCH v3 3/3] media: uvcvideo: Introduce V4L2_META_FMT_UVC

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]

Message-ID: <20250314073456.25817a3d@foz.lan>
Date: Fri, 14 Mar 2025 07:34:56 +0100
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Ricardo Ribalda <ribalda@...omium.org>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>, Laurent Pinchart
 <laurent.pinchart@...asonboard.com>, Hans de Goede <hdegoede@...hat.com>,
 Guennadi Liakhovetski <guennadi.liakhovetski@...el.com>,
 linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] media: uvcvideo: Introduce
 V4L2_META_FMT_UVC_CUSTOM

Em Thu, 13 Mar 2025 12:06:27 +0000
Ricardo Ribalda <ribalda@...omium.org> escreveu:

> The UVC driver provides two metadata types V4L2_META_FMT_UVC, and
> V4L2_META_FMT_D4XX. The only difference between the two of them is that
> V4L2_META_FMT_UVC only copies PTS, SCR, size and flags, and
> V4L2_META_FMT_D4XX copies the whole metadata section.
> 
> Now we only enable V4L2_META_FMT_D4XX for the Intel D4xx family of
> devices, but it is useful to have the whole metadata section for any
> device where vendors include other metadata, such as the one described by
> Microsoft:
> https://learn.microsoft.com/en-us/windows-hardware/drivers/stream/mf-capture-metadata
> 
> This patch introduces a new format V4L2_META_FMT_UVC_CUSTOM, that is
> identical to V4L2_META_FMT_D4XX but it is available to all the UVC
> devices.
> 
> Suggested-by: Hans de Goede <hdegoede@...hat.com>
> Signed-off-by: Ricardo Ribalda <ribalda@...omium.org>
> ---
>  .../userspace-api/media/v4l/meta-formats.rst       |  1 +
>  .../userspace-api/media/v4l/metafmt-uvc-custom.rst | 31 +++++++++++++++++
>  MAINTAINERS                                        |  1 +
>  drivers/media/usb/uvc/uvc_metadata.c               | 40 ++++++++++++++++++----
>  drivers/media/v4l2-core/v4l2-ioctl.c               |  1 +
>  include/uapi/linux/videodev2.h                     |  1 +
>  6 files changed, 69 insertions(+), 6 deletions(-)
> 
> diff --git a/Documentation/userspace-api/media/v4l/meta-formats.rst b/Documentation/userspace-api/media/v4l/meta-formats.rst
> index 86ffb3bc8ade2e0c563dd84441572ecea1a571a6..9fd83f4a3cc8509702a2a9f032fdc04bf6c6d1bc 100644
> --- a/Documentation/userspace-api/media/v4l/meta-formats.rst
> +++ b/Documentation/userspace-api/media/v4l/meta-formats.rst
> @@ -19,6 +19,7 @@ These formats are used for the :ref:`metadata` interface only.
>      metafmt-pisp-fe
>      metafmt-rkisp1
>      metafmt-uvc
> +    metafmt-uvc-custom
>      metafmt-vivid
>      metafmt-vsp1-hgo
>      metafmt-vsp1-hgt
> diff --git a/Documentation/userspace-api/media/v4l/metafmt-uvc-custom.rst b/Documentation/userspace-api/media/v4l/metafmt-uvc-custom.rst
> new file mode 100644
> index 0000000000000000000000000000000000000000..9f150fc2b6f379cc4707ff45041dd014956ae11a
> --- /dev/null
> +++ b/Documentation/userspace-api/media/v4l/metafmt-uvc-custom.rst
> @@ -0,0 +1,31 @@
> +.. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
> +
> +.. _v4l2-meta-fmt-uvc-custom:
> +
> +*********************************
> +V4L2_META_FMT_UVC_CUSTOM ('UVCC')
> +*********************************
> +
> +UVC Custom Payload Metadata.
> +
> +
> +Description
> +===========
> +
> +V4L2_META_FMT_UVC_CUSTOM buffers follow the metadata buffer layout of
> +V4L2_META_FMT_UVC with the only difference that it includes all the UVC
> +metadata, not just the first 2-12 bytes.
> +
> +The most common metadata format is the one proposed by Microsoft(R)'s UVC
> +extension [1_], but other vendors might have different formats.
> +
> +Applications might use information from the Hardware Database (hwdb)[2_] to
> +process the camera's metadata accordingly.

Having something like that at the userspace API shouldn't be handled
lightly. This sounds to me that passing a blank check for vendors to stream
whatever they want without any requirements to provide and sort of
documentation for the usersace to decode it.

Also, it would be hard for userspace to distinguish what metatata
is contained for a random UVC camera. Please let's not do that.

As the specific issue here is to support an already known extension,
which is already documented, Just add an specific format for it, e.g. 
you could add something like that at the documentation:

	V4L2_META_FMT_MSXU_UVC_1_5
	   Microsoft extensions to USB Video Class 1.5 specification.
	
	   For more details, see: https://learn.microsoft.com/en-us/windows-hardware/drivers/stream/uvc-extensions-1-5	

And then add the corresponding format to V4L2 API.

Regards,
Mauro