From: Borislav Petkov <bp@alien8.de>
To: syzbot <syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com>
Cc: anna.schumaker@netapp.com, bfields@fieldses.org,
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: Tue, 2 Apr 2019 10:26:02 +0200 [thread overview]
Message-ID: <20190402082602.GA6826@zn.tnic> (raw)
In-Reply-To: <000000000000bd253c058585101e@google.com>
On Mon, Apr 01, 2019 at 10:04:01PM -0700, syzbot wrote:
> 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'
That looks like the bisection is at least imprecise, if not gone into
the weeds.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-04-02 8:26 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
2019-04-02 8:26 ` Borislav Petkov [this message]
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=20190402082602.GA6826@zn.tnic \
--to=bp@alien8.de \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--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=syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.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.