From: Benjamin Gaignard <benjamin.gaignard@collabora.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Tomasz Figa <tfiga@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Hans Verkuil <hverkuil@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] media: videobuf2: forbid create_bufs/remove_bufs when legacy fileio is active
Date: Mon, 20 Oct 2025 09:11:25 +0200 [thread overview]
Message-ID: <36cfec0a-3717-4b0e-adc0-6887e6b58f44@collabora.com> (raw)
In-Reply-To: <20251016111154.993949-1-m.szyprowski@samsung.com>
Le 16/10/2025 à 13:11, Marek Szyprowski a écrit :
> create_bufs and remove_bufs ioctl calls manipulate queue internal buffer
> list, potentially overwriting some pointers used by the legacy fileio
> access mode. Simply forbid those calls when fileio is active to protect
> internal queue state between subsequent read/write calls.
Hi Marek,
I may be wrong but using fileio API and create/remove API at the same time
sound incorrect from application point of view, right ? If that not the
case maybe we should also add a test in v4l2-compliance.
Regards,
Benjamin
>
> CC: stable@vger.kernel.org
> Fixes: 2d86401c2cbf ("[media] V4L: vb2: add support for buffers of different sizes on a single queue")
> Fixes: a3293a85381e ("media: v4l2: Add REMOVE_BUFS ioctl")
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/media/common/videobuf2/videobuf2-v4l2.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/media/common/videobuf2/videobuf2-v4l2.c b/drivers/media/common/videobuf2/videobuf2-v4l2.c
> index d911021c1bb0..f4104d5971dd 100644
> --- a/drivers/media/common/videobuf2/videobuf2-v4l2.c
> +++ b/drivers/media/common/videobuf2/videobuf2-v4l2.c
> @@ -751,6 +751,11 @@ int vb2_create_bufs(struct vb2_queue *q, struct v4l2_create_buffers *create)
> int ret = vb2_verify_memory_type(q, create->memory, f->type);
> unsigned i;
>
> + if (vb2_fileio_is_active(q)) {
> + dprintk(q, 1, "file io in progress\n");
> + return -EBUSY;
> + }
> +
> create->index = vb2_get_num_buffers(q);
> vb2_set_flags_and_caps(q, create->memory, &create->flags,
> &create->capabilities, &create->max_num_buffers);
> @@ -1010,6 +1015,11 @@ int vb2_ioctl_remove_bufs(struct file *file, void *priv,
> if (vb2_queue_is_busy(vdev->queue, file))
> return -EBUSY;
>
> + if (vb2_fileio_is_active(vdev->queue)) {
> + dprintk(vdev->queue, 1, "file io in progress\n");
> + return -EBUSY;
> + }
> +
> return vb2_core_remove_bufs(vdev->queue, d->index, d->count);
> }
> EXPORT_SYMBOL_GPL(vb2_ioctl_remove_bufs);
next prev parent reply other threads:[~2025-10-20 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251016111208eucas1p24cd8cc1e952a8cdf73fbadea704b499d@eucas1p2.samsung.com>
2025-10-16 11:11 ` Marek Szyprowski
2025-10-20 7:11 ` Benjamin Gaignard [this message]
2025-10-20 7:34 ` Marek Szyprowski
2025-10-20 7:39 ` Hans Verkuil
2025-10-20 7:48 ` Benjamin Gaignard
2025-10-20 8:21 ` Marek Szyprowski
2025-10-20 8:30 ` Benjamin Gaignard
2025-10-20 16:05 ` Marek Szyprowski
2025-10-20 7:36 ` Marek Szyprowski
2025-10-18 18:34 Bai, Shuangpeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36cfec0a-3717-4b0e-adc0-6887e6b58f44@collabora.com \
--to=benjamin.gaignard@collabora.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®