From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, acme@kernel.org,
eranian@google.com, jolsa@redhat.com,
alexander.shishkin@linux.intel.com
Subject: Re: [RFC][PATCH 0/3] variuos perf fixes
Date: Mon, 14 Sep 2015 08:57:48 +0200 [thread overview]
Message-ID: <20150914065748.GL18489@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1509131904590.23554@vincent-weaver-1.umelst.maine.edu>
On Sun, Sep 13, 2015 at 07:10:56PM -0400, Vince Weaver wrote:
> On Thu, 10 Sep 2015, Peter Zijlstra wrote:
>
> > Vince reported some fail here:
> >
> > lkml.kernel.org/r/alpine.DEB.2.20.1509021227380.32729@vincent-weaver-1.umelst.maine.edu
> >
> > These patches are the result of me trying to fix it.
> >
> > Compile tested only, I'll try them after a sleep..
>
> Sorry for the delay testing, your e-mails continue being sent to SPAM by
> gmail for some reason.
>
> I patched up a 4.3-rc1 system with the patches, and pretty much my
> *entire* perf_event test suite causes kernel oopses.
>
> This is on an AMD a10 system.
>
> [ 1564.442224] BUG: unable to handle kernel NULL pointer dereference at 00000000000001e8
Yeah, I really should just not set out patches when I'm that tired.
What's worse, I already fixed this splat once, but forgot to copy it
over to the right machine etc..
Total fail.
prev parent reply other threads:[~2015-09-14 6:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 16:16 [RFC][PATCH 0/3] variuos perf fixes Peter Zijlstra
2015-09-10 16:16 ` [RFC][PATCH 1/3] perf: Restructure perf syscall point of no return Peter Zijlstra
2015-09-10 16:16 ` [RFC][PATCH 2/3] perf: Fix u16 overflows Peter Zijlstra
2015-09-12 8:11 ` Ingo Molnar
2015-09-14 9:06 ` Peter Zijlstra
2015-09-14 9:31 ` Ingo Molnar
2015-09-10 16:16 ` [RFC][PATCH 3/3] perf: Fix races in computing the header sizes Peter Zijlstra
2015-09-13 23:10 ` [RFC][PATCH 0/3] variuos perf fixes Vince Weaver
2015-09-14 6:57 ` Peter Zijlstra [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=20150914065748.GL18489@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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.