From: syzbot <syzbot+e417648b303855b91d8a@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,
syzkaller-bugs@googlegroups.com, wsa@kernel.org
Subject: Re: [syzbot] WARNING in __i2c_transfer (2)
Date: Wed, 08 Dec 2021 08:50:21 -0800 [thread overview]
Message-ID: <0000000000001bab9705d2a549cb@google.com> (raw)
In-Reply-To: <000000000000b5e7f105d0d2d165@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=152b58b1b00000
start commit: cd8c917a56f2 Makefile: Do not quote value for CONFIG_CC_IM..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=172b58b1b00000
console output: https://syzkaller.appspot.com/x/log.txt?x=132b58b1b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=221ffc09e39ebbd1
dashboard link: https://syzkaller.appspot.com/bug?extid=e417648b303855b91d8a
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a68531b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b91d89b00000
Reported-by: syzbot+e417648b303855b91d8a@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-12-08 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:19 [syzbot] WARNING in __i2c_transfer (2) syzbot
2021-12-07 22:06 ` syzbot
2021-12-08 16:50 ` syzbot [this message]
2021-12-25 12:39 ` Pavel Skripkin
2021-12-25 12:50 ` 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=0000000000001bab9705d2a549cb@google.com \
--to=syzbot+e417648b303855b91d8a@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=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.