From: syzbot <syzbot+809dfc586f33fc44b6ac@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, neganhat@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] [usb?] kernel BUG in v4l2_device_put
Date: Thu, 22 Oct 2026 09:58:02 -0700 [thread overview]
Message-ID: <6ada409a.d1c214cc.659fa.00dc.GAE@google.com> (raw)
In-Reply-To: <CAFJkwZzqQtu6K7xYdJMp8Wm3DEa-Psp4tiyPxi_H=gcWygT6uA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+809dfc586f33fc44b6ac@syzkaller.appspotmail.com
Tested-by: syzbot+809dfc586f33fc44b6ac@syzkaller.appspotmail.com
Tested on:
commit: 8f7df005 Add linux-next specific files for 20261020
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=155a9fa9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9c1b9b13e3e4ce1a
dashboard link: https://syzkaller.appspot.com/bug?extid=809dfc586f33fc44b6ac
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=12170f99580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-10-22 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFJkwZzqQtu6K7xYdJMp8Wm3DEa-Psp4tiyPxi_H=gcWygT6uA@mail.gmail.com>
2026-10-22 16:58 ` syzbot [this message]
[not found] <20261101203949.184-1-drifabdelmalekmohamedsaid@gmail.com>
2026-11-02 0:27 ` [syzbot] [media?] [usb?] kernel BUG in v4l2_device_put syzbot
[not found] <CAFJkwZzN_bRRY4hqa1upEsCmnXyMeYdUd-4dKhO9_8vvuwVc4g@mail.gmail.com>
2026-10-22 15:40 ` syzbot
[not found] <CAFJkwZzx+CfBNYxfzToB-0iKrr1=MB6bxh8ySU7uApxyQXm-PA@mail.gmail.com>
2026-10-22 14:08 ` syzbot
2026-10-22 0:29 syzbot
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=6ada409a.d1c214cc.659fa.00dc.GAE@google.com \
--to=syzbot+809dfc586f33fc44b6ac@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neganhat@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.