From: syzbot <syzbot+78dbea1c214b5413bdd3@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, jdelvare@suse.com,
jiapeng.chong@linux.alibaba.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in clear_state_bit
Date: Fri, 25 Nov 2022 09:49:21 -0800 [thread overview]
Message-ID: <0000000000003f5a8205ee4f2429@google.com> (raw)
In-Reply-To: <000000000000a9ccd705ee4865be@google.com>
syzbot has bisected this issue to:
commit 4444a06981af66a49cf0cd08fec9759e8dd0a0fc
Author: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Date: Thu Sep 1 02:23:32 2022 +0000
hwmon: (emc2305) Remove unused including <linux/version.h>
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=161ba58d880000
start commit: c3eb11fbb826 Merge tag 'pci-v6.1-fixes-3' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=151ba58d880000
console output: https://syzkaller.appspot.com/x/log.txt?x=111ba58d880000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d01b6e3197974dd
dashboard link: https://syzkaller.appspot.com/bug?extid=78dbea1c214b5413bdd3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149d9403880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14a0d8e3880000
Reported-by: syzbot+78dbea1c214b5413bdd3@syzkaller.appspotmail.com
Fixes: 4444a06981af ("hwmon: (emc2305) Remove unused including <linux/version.h>")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-11-25 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 9:46 [syzbot] kernel BUG in clear_state_bit syzbot
2022-11-25 17:49 ` 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=0000000000003f5a8205ee4f2429@google.com \
--to=syzbot+78dbea1c214b5413bdd3@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jdelvare@suse.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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