From: syzbot <syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com>
To: benjamin.gaignard@collabora.com, daniel.almeida@collabora.com,
hdanton@sina.com, hverkuil-cisco@xs4all.nl,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab@kernel.org, nicolas.dufresne@collabora.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] possible deadlock in v4l2_ctrl_handler_log_status
Date: Fri, 09 Feb 2024 05:58:02 -0800 [thread overview]
Message-ID: <000000000000ff69600610f35011@google.com> (raw)
In-Reply-To: <000000000000ce2dde0610db47a8@google.com>
syzbot has bisected this issue to:
commit 9801b5b28c6929139d6fceeee8d739cc67bb2739
Author: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Date: Wed Jan 17 14:52:04 2024 +0000
media: v4l2-ctrls: show all owned controls in log_status
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1278acec180000
start commit: b1d3a0e70c38 Add linux-next specific files for 20240208
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1178acec180000
console output: https://syzkaller.appspot.com/x/log.txt?x=1678acec180000
kernel config: https://syzkaller.appspot.com/x/.config?x=bb693ba195662a06
dashboard link: https://syzkaller.appspot.com/bug?extid=9948f8e188482c5d1a3e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148953c4180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1746f9b7e80000
Reported-by: syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com
Fixes: 9801b5b28c69 ("media: v4l2-ctrls: show all owned controls in log_status")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-02-09 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 9:17 [syzbot] [media?] possible deadlock in v4l2_ctrl_handler_log_status syzbot
2024-02-09 8:11 ` Hillf Danton
2024-02-09 8:34 ` syzbot
2024-02-09 13:58 ` syzbot [this message]
2024-07-24 12:57 ` 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=000000000000ff69600610f35011@google.com \
--to=syzbot+9948f8e188482c5d1a3e@syzkaller.appspotmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=daniel.almeida@collabora.com \
--cc=hdanton@sina.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox