From: syzbot <syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com>
To: anna.schumaker@netapp.com, bfields@fieldses.org, bp@alien8.de,
davem@davemloft.net, douly.fnst@cn.fujitsu.com, hpa@zytor.com,
jlayton@kernel.org, konrad.wilk@oracle.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, puwen@hygon.cn,
rafael.j.wysocki@intel.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, trond.myklebust@hammerspace.com,
trond.myklebust@primarydata.com, vbabka@suse.cz, x86@kernel.org
Subject: Re: WARNING: ODEBUG bug in __do_softirq
Date: Mon, 01 Apr 2019 22:04:01 -0700 [thread overview]
Message-ID: <000000000000bd253c058585101e@google.com> (raw)
In-Reply-To: <001a1143e62eb6a9510565640e76@google.com>
syzbot has bisected this bug to:
commit 5b317cbf2bcb85a1e96ce87717cb991ecab1dd4d
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Fri Feb 22 09:17:11 2019 +0000
Merge branch 'pm-cpufreq-fixes'
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=171ead5d200000
start commit: e60b5f79 Merge tag 'powerpc-5.0-6' of git://git.kernel.org..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=149ead5d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=109ead5d200000
kernel config: https://syzkaller.appspot.com/x/.config?x=7132344728e7ec3f
dashboard link: https://syzkaller.appspot.com/bug?extid=51c9bdfa559769d2f897
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16591514c00000
Reported-by: syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com
Fixes: 5b317cbf2bcb ("Merge branch 'pm-cpufreq-fixes'")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-04-02 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 8:15 WARNING: ODEBUG bug in __do_softirq syzbot
2018-06-29 8:58 ` syzbot
2019-04-02 5:04 ` syzbot [this message]
2019-04-02 8:26 ` Borislav Petkov
2020-08-26 8:54 ` syzbot
2020-08-26 11:03 ` Thomas Gleixner
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=000000000000bd253c058585101e@google.com \
--to=syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=jlayton@kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=trond.myklebust@hammerspace.com \
--cc=trond.myklebust@primarydata.com \
--cc=vbabka@suse.cz \
--cc=x86@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.