From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: perf: perf_fuzzer crashes on Pentium 4 systems
Date: Thu, 4 Apr 2019 16:33:27 +0300 [thread overview]
Message-ID: <20190404133327.GP1421@uranus.lan> (raw)
In-Reply-To: <alpine.DEB.2.21.1904040922350.3758@macbook-air>
On Thu, Apr 04, 2019 at 09:25:47AM -0400, Vince Weaver wrote:
>
> It looks like there are at least two bugs here, one that's a full
> hardlockup with nothing on serial console. The other is the NULL
> dereference.
>
Seems so. I've spent plenty of time yesterday trying to figure out how
we even reach the case when event = nil but without much luck.
> Just ran with your patch applied and it hit the hard lockup case.
>
> I'll have to see if things are reproducible and I can try to see if I can
> get a reproducible value for what even caused the issue. perf_fuzzer has
> some infrastructure for determining that but it's hit or miss if you can
> get anything useful from it.
At least the sequence of events migh give us some ideas, maybe not indeed.
Thanks a huge, Vince!
> I'll keep running things, but I'm a bit busy at work here the next few
> days so there might be some delay in the results.
Sure, take your time. I think this problem with p4 is not urgent. I'll ping
you if I get some more ideas.
next prev parent reply other threads:[~2019-04-04 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:59 perf: perf_fuzzer crashes on Pentium 4 systems Vince Weaver
2019-04-03 15:13 ` Cyrill Gorcunov
2019-04-03 19:19 ` Cyrill Gorcunov
2019-04-03 20:31 ` Cyrill Gorcunov
2019-04-04 13:25 ` Vince Weaver
2019-04-04 13:33 ` Cyrill Gorcunov [this message]
2019-04-04 16:37 ` Vince Weaver
2019-04-04 16:47 ` Cyrill Gorcunov
2019-04-04 19:01 ` Vince Weaver
2019-04-04 20:20 ` Cyrill Gorcunov
2019-04-07 20:20 ` Cyrill Gorcunov
2019-04-09 16:38 ` Vince Weaver
2019-04-09 17:00 ` Cyrill Gorcunov
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=20190404133327.GP1421@uranus.lan \
--to=gorcunov@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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.