Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1468851
| From | Vince Weaver <vince@deater.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent |
| Date | 2016-08-23 23:00 +0200 |
| Message-ID | <s9qXE-H7-21@gated-at.bofh.it> (permalink) |
| References | <s9fIR-1yv-11@gated-at.bofh.it> <s9mKl-6om-23@gated-at.bofh.it> <s9nwJ-6Yb-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 23 Aug 2016, Alexander Shishkin wrote: > 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. Just wanted to say that when I backed out these patches the NMI errors went away, so they do seem to be a result of this patch series. Vince
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-23 11:00 +0200
[PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-23 11:00 +0200
Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-24 14:30 +0200
Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-24 16:20 +0200
[PATCH 3/3] perf: Fix a race between mmap_close and set_output of AUX events Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-23 11:00 +0200
[PATCH 2/3] perf/x86/intel/bts: Kill a silly warning Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-23 11:00 +0200
Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Vince Weaver <vince@deater.net> - 2016-08-23 18:30 +0200
Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-23 19:20 +0200
Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Vince Weaver <vince@deater.net> - 2016-08-23 23:00 +0200
Re: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-08-24 05:50 +0200
csiph-web