From: Finn Thain <fthain@telegraphics.com.au>
To: syzbot <syzbot+a41ac89a0712acde0e84@syzkaller.appspotmail.com>
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
funaho@jurai.org, geert@linux-m68k.org, jolsa@redhat.com,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: rcu detected stall in __perf_sw_event
Date: Wed, 27 Mar 2019 10:28:19 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1903271021290.994@nippy.intranet> (raw)
In-Reply-To: <00000000000036e81e058507565b@google.com>
On Tue, 26 Mar 2019, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit cf85d89562f39cc7ae73de54639f1915a9195b7a
> Author: Finn Thain <fthain@telegraphics.com.au>
> Date: Fri May 25 07:34:36 2018 +0000
>
> m68k/mac: Enable PDMA for PowerBook 500 series
>
Looks like a false positive. But if you really are running syzkaller on a
PowerBook 500, you'll want to check that you have an FPU, otherwise a CPU
erratum will probably mess up your results.
--
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1226cb8b200000
> start commit: b0314565 Merge tag 'for_linus' of git://git.kernel.org/pub..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1126cb8b200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1626cb8b200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8f00801d7b7c4fe6
> dashboard link: https://syzkaller.appspot.com/bug?extid=a41ac89a0712acde0e84
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1707cd2f400000
>
> Reported-by: syzbot+a41ac89a0712acde0e84@syzkaller.appspotmail.com
> Fixes: cf85d89562f3 ("m68k/mac: Enable PDMA for PowerBook 500 series")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-03-26 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 15:07 syzbot
2019-03-26 23:04 ` syzbot
2019-03-26 23:28 ` Finn Thain [this message]
2019-03-28 8:21 ` Dmitry Vyukov
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=alpine.LNX.2.21.1903271021290.994@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+a41ac89a0712acde0e84@syzkaller.appspotmail.com \
--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
all inboxes | Powered by JetHome®