From: syzbot <syzbot+116b65a23bc791ae49a6@syzkaller.appspotmail.com>
To: bryan.odonoghue@linaro.org, eadavis@qq.com, hdanton@sina.com,
hverkuil-cisco@xs4all.nl, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
ribalda@chromium.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] INFO: task hung in cec_claim_log_addrs
Date: Sun, 23 Jun 2024 07:16:02 -0700 [thread overview]
Message-ID: <000000000000f51641061b8f4d2c@google.com> (raw)
In-Reply-To: <0000000000006d96200611de3986@google.com>
syzbot suspects this issue was fixed by commit:
commit 2998b976300d087db739f044a105c88573f031d4
Author: Ricardo Ribalda <ribalda@chromium.org>
Date: Mon Apr 29 15:04:52 2024 +0000
media: common: saa7146: Use min macro
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17ba1dda980000
start commit: 45ec2f5f6ed3 Merge tag 'mtd/fixes-for-6.8-rc7' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fad652894fc96962
dashboard link: https://syzkaller.appspot.com/bug?extid=116b65a23bc791ae49a6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b2f122180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11fd704c180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: media: common: saa7146: Use min macro
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-23 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 6:13 [syzbot] [media?] INFO: task hung in cec_claim_log_addrs syzbot
2024-02-21 12:29 ` Hillf Danton
2024-02-21 13:53 ` syzbot
2024-02-21 13:13 ` Edward Adam Davis
2024-02-21 14:18 ` syzbot
2024-02-21 14:20 ` [PATCH] media/cec/core: fix " Edward Adam Davis
2024-02-21 14:38 ` Hans Verkuil
2024-02-22 10:43 ` Hillf Danton
2024-02-22 12:16 ` Hans Verkuil
2024-02-22 10:58 ` Edward Adam Davis
2024-02-22 4:58 ` [syzbot] [media?] INFO: " Hillf Danton
2024-02-22 5:30 ` syzbot
2024-06-23 14:16 ` 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=000000000000f51641061b8f4d2c@google.com \
--to=syzbot+116b65a23bc791ae49a6@syzkaller.appspotmail.com \
--cc=bryan.odonoghue@linaro.org \
--cc=eadavis@qq.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=ribalda@chromium.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