From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Vince Weaver <vince@deater.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, eranian@google.com,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent
Date: Tue, 23 Aug 2016 20:10:34 +0300 [thread overview]
Message-ID: <87shtvl8c5.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1608231223310.3428@pianoman.cluster.toy>
Vince Weaver <vince@deater.net> writes:
> On Tue, 23 Aug 2016, Alexander Shishkin wrote:
>
>> Recently Vince has reported warnings and panics coming from the
>> general direction of AUX tracing. I found two bugs which manifest
>> similarly, one in intel_bts driver and one in AUX unmapping path.
>>
>> Both are triggered by racing SET_OUTPUT against mmap_close while
>> running AUX tracing. I have a test case that set fire to the kernel
>> within a few seconds by doing this, which I can share if anyone
>> cares.
>
> I've applied these and am fuzzing on my Haswell machine and I'm getting
> lots and lots of
>
> [ 945.536374] Dazed and confused, but trying to continue
> [ 945.542391] Uhhuh. NMI received for unknown reason 21 on CPU 2.
> [ 945.549360] Do you have a strange power saving mode enabled?
> [ 945.556701] Dazed and confused, but trying to continue
> [ 945.563643] Uhhuh. NMI received for unknown reason 31 on CPU 2.
> [ 945.571379] Do you have a strange power saving mode enabled?
> [ 945.578754] Dazed and confused, but trying to continue
> [ 945.630889] Uhhuh. NMI received for unknown reason 31 on CPU 2.
> [ 945.638141] Do you have a strange power saving mode enabled?
> [ 945.645523] Dazed and confused, but trying to continue
>
> messages that I wasn't getting before. Of course, I updated from -rc2 to
> -rc3 before applying the patch so it could also be related to that too, I
> can try backing out the patches and see if it still happens.
Uhhuh, that's not cool, let me look some more. But it should stop dying
on bts/aux stuff at least.
Regards,
--
Alex
next prev parent reply other threads:[~2016-08-23 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 8:54 [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Alexander Shishkin
2016-08-23 8:54 ` [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin
2016-08-24 12:28 ` Alexander Shishkin
2016-08-24 14:15 ` Alexander Shishkin
2016-08-26 20:49 ` Vince Weaver
2016-08-27 6:35 ` Alexander Shishkin
2016-08-29 14:14 ` Peter Zijlstra
2016-08-29 14:43 ` Alexander Shishkin
2016-08-23 8:54 ` [PATCH 2/3] perf/x86/intel/bts: Kill a silly warning Alexander Shishkin
2016-08-23 8:54 ` [PATCH 3/3] perf: Fix a race between mmap_close and set_output of AUX events Alexander Shishkin
2016-08-23 16:24 ` [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Vince Weaver
2016-08-23 17:10 ` Alexander Shishkin [this message]
2016-08-23 20:55 ` Vince Weaver
2016-08-24 3:44 ` Alexander Shishkin
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=87shtvl8c5.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=vince@deater.net \
/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;
as well as URLs for NNTP newsgroup(s).