From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Rohinthan P <rokinthanp03@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+f26bc23e42eeb548dee1@syzkaller.appspotmail.com
Subject: Re: [PATCH] media: em28xx: use video_unregister_device for radio_dev
Date: Wed, 23 Sep 2026 14:12:51 +0200 [thread overview]
Message-ID: <32a27d02-a6fc-4006-8fb0-78061afa0f3d@kernel.org> (raw)
In-Reply-To: <20260923072050.24427-1-rokinthanp03@gmail.com>
On 23/09/2026 09:20, Rohinthan P wrote:
> Commit 7c8bf63b7937 ("media: em28xx: use vb2_video_unregister_device")
> converted device unregistrations in em28xx to use
> vb2_video_unregister_device() instead of video_unregister_device().
>
> However, radio devices do not have an associated videobuf2 queue
> (v4l2->radio_dev.queue is NULL). Calling vb2_video_unregister_device()
> on a radio device triggers a WARNING in vb2_video_unregister_device():
>
> !vdev->queue
> WARNING: drivers/media/common/videobuf2/videobuf2-v4l2.c:1264 at vb2_video_unregister_device+0x1f8/0x200
> Call Trace:
> em28xx_v4l2_init+0x1c39/0x3150 drivers/media/usb/em28xx/em28xx-video.c:3085
>
> As documented in vb2_video_unregister_device(), video_unregister_device()
> should be used instead when vdev->queue is NULL.
>
> Revert to calling video_unregister_device() for v4l2->radio_dev in both
> em28xx_v4l2_fini() and the em28xx_v4l2_init() error unwind path.
Good catch!
This is actually a fix for the 7.3-rcX mainline.
I'll handle this.
Regards,
Hans
>
> Fixes: 7c8bf63b7937 ("media: em28xx: use vb2_video_unregister_device")
> Reported-by: syzbot+f26bc23e42eeb548dee1@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=f26bc23e42eeb548dee1
> Signed-off-by: Rohinthan P <rokinthanp03@gmail.com>
> ---
> drivers/media/usb/em28xx/em28xx-video.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/usb/em28xx/em28xx-video.c b/drivers/media/usb/em28xx/em28xx-video.c
> index c418add..79af154 100644
> --- a/drivers/media/usb/em28xx/em28xx-video.c
> +++ b/drivers/media/usb/em28xx/em28xx-video.c
> @@ -2416,7 +2416,7 @@ static int em28xx_v4l2_fini(struct em28xx *dev)
> if (video_is_registered(&v4l2->radio_dev)) {
> dev_info(&dev->intf->dev, "V4L2 device %s deregistered\n",
> video_device_node_name(&v4l2->radio_dev));
> - vb2_video_unregister_device(&v4l2->radio_dev);
> + video_unregister_device(&v4l2->radio_dev);
> }
> if (video_is_registered(&v4l2->vbi_dev)) {
> dev_info(&dev->intf->dev, "V4L2 device %s deregistered\n",
> @@ -3082,7 +3082,7 @@ static int em28xx_v4l2_init(struct em28xx *dev)
> dev_info(&dev->intf->dev,
> "V4L2 device %s deregistered\n",
> video_device_node_name(&v4l2->radio_dev));
> - vb2_video_unregister_device(&v4l2->radio_dev);
> + video_unregister_device(&v4l2->radio_dev);
> }
> if (video_is_registered(&v4l2->vbi_dev)) {
> dev_info(&dev->intf->dev,
prev parent reply other threads:[~2026-09-23 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:20 Rohinthan P
2026-09-23 12:12 ` Hans Verkuil [this message]
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=32a27d02-a6fc-4006-8fb0-78061afa0f3d@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rokinthanp03@gmail.com \
--cc=syzbot+f26bc23e42eeb548dee1@syzkaller.appspotmail.com \
/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®