From: syzbot <syzbot+ffb0b3ffa6cfbc7d7b3f@syzkaller.appspotmail.com>
To: dwlsalmeida@gmail.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mchehab+huawei@kernel.org, mchehab@kernel.org,
paskripkin@gmail.com, syzkaller-bugs@googlegroups.com,
wsa@kernel.org
Subject: Re: [syzbot] WARNING in __i2c_transfer
Date: Fri, 12 Mar 2021 02:09:08 -0800 [thread overview]
Message-ID: <0000000000003ceac005bd541781@google.com> (raw)
In-Reply-To: <000000000000f564d305bd521b83@google.com>
syzbot has bisected this issue to:
commit f90cf6079bf67988f8b1ad1ade70fc89d0080905
Author: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
Date: Fri Aug 21 12:58:47 2020 +0000
media: vidtv: add a bridge driver
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1136cf66d00000
start commit: 28806e4d Merge tag 'media/v5.12-2' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1336cf66d00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1536cf66d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6bcf96204c1b8e77
dashboard link: https://syzkaller.appspot.com/bug?extid=ffb0b3ffa6cfbc7d7b3f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1083223ad00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14345f0ad00000
Reported-by: syzbot+ffb0b3ffa6cfbc7d7b3f@syzkaller.appspotmail.com
Fixes: f90cf6079bf6 ("media: vidtv: add a bridge driver")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-03-12 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 7:47 [syzbot] WARNING in __i2c_transfer syzbot
2021-03-12 9:13 ` Wolfram Sang
2021-03-12 10:09 ` syzbot [this message]
2021-03-12 11:46 ` Wolfram Sang
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=0000000000003ceac005bd541781@google.com \
--to=syzbot+ffb0b3ffa6cfbc7d7b3f@syzkaller.appspotmail.com \
--cc=dwlsalmeida@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=paskripkin@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wsa@kernel.org \
/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.