From: syzbot <syzbot+0591ccf54ee05344e4eb@syzkaller.appspotmail.com>
To: akhilrajeev@nvidia.com, andriy.shevchenko@linux.intel.com,
andy.shevchenko@gmail.com, djrscally@gmail.com,
gregkh@linuxfoundation.org, heikki.krogerus@linux.intel.com,
johan@kernel.org, linux-acpi@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, sakari.ailus@linux.intel.com,
syzkaller-bugs@googlegroups.com, wsa@kernel.org
Subject: Re: [syzbot] general protection fault in i2c_setup_smbus_alert
Date: Thu, 10 Feb 2022 19:51:08 -0800 [thread overview]
Message-ID: <0000000000001a5dc005d7b5fab1@google.com> (raw)
In-Reply-To: <0000000000006e988105d72fbe3f@google.com>
syzbot has bisected this issue to:
commit a263a84088f689bf0c1552a510b25d0bcc45fcae
Author: Akhil R <akhilrajeev@nvidia.com>
Date: Fri Jan 28 11:44:27 2022 +0000
i2c: smbus: Use device_*() functions instead of of_*()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=156c8174700000
start commit: ef6b35306dd8 Add linux-next specific files for 20220204
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=176c8174700000
console output: https://syzkaller.appspot.com/x/log.txt?x=136c8174700000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0431e0b00810b4f
dashboard link: https://syzkaller.appspot.com/bug?extid=0591ccf54ee05344e4eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1105f472700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16492aa4700000
Reported-by: syzbot+0591ccf54ee05344e4eb@syzkaller.appspotmail.com
Fixes: a263a84088f6 ("i2c: smbus: Use device_*() functions instead of of_*()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-02-11 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 11:42 [syzbot] general protection fault in i2c_setup_smbus_alert syzbot
2022-02-11 0:37 ` syzbot
2022-02-11 3:51 ` syzbot [this message]
2022-02-11 8:38 ` Andy Shevchenko
2022-02-11 8:49 ` Akhil R
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=0000000000001a5dc005d7b5fab1@google.com \
--to=syzbot+0591ccf54ee05344e4eb@syzkaller.appspotmail.com \
--cc=akhilrajeev@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=johan@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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.