From: syzbot <syzbot+701fc9cc0cb44e2b0fe9@syzkaller.appspotmail.com>
To: cascardo@igalia.com, gshahrouzi@gmail.com, hansg@kernel.org,
hdegoede@redhat.com, hverkuil+cisco@kernel.org,
kernelmentees@lists.linuxfoundation.org,
laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
mchehab@kernel.org, ribalda@chromium.org,
sakari.ailus@linux.intel.com, skhan@linuxfoundation.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [media?] WARNING in media_create_pad_link (2)
Date: Wed, 12 Nov 2025 16:45:02 -0800 [thread overview]
Message-ID: <69152a0e.a70a0220.3124cb.000f.GAE@google.com> (raw)
In-Reply-To: <67da6f4b.050a0220.3657bb.013b.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 0e2ee70291e64a30fe36960c85294726d34a103e
Author: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Date: Wed Aug 20 16:08:16 2025 +0000
media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f0f0b4580000
start commit: 07e27ad16399 Linux 6.17-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4d8792ecb6308d0f
dashboard link: https://syzkaller.appspot.com/bug?extid=701fc9cc0cb44e2b0fe9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e38142580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12da427c580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-11-13 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 7:16 [syzbot] [media?] [usb?] WARNING in media_create_pad_link (2) syzbot
2025-11-13 0:45 ` syzbot [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=69152a0e.a70a0220.3124cb.000f.GAE@google.com \
--to=syzbot+701fc9cc0cb44e2b0fe9@syzkaller.appspotmail.com \
--cc=cascardo@igalia.com \
--cc=gshahrouzi@gmail.com \
--cc=hansg@kernel.org \
--cc=hdegoede@redhat.com \
--cc=hverkuil+cisco@kernel.org \
--cc=kernelmentees@lists.linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=skhan@linuxfoundation.org \
--cc=syzkaller-bugs@googlegroups.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