From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Vince Weaver <vincent.weaver@maine.edu>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: perf_fuzzer WARNING: ring_buffer.c:546 __rb_free_aux
Date: Thu, 10 Nov 2016 16:54:20 +0200 [thread overview]
Message-ID: <87a8d7o06b.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1610232354480.28422@macbook-air>
Vince Weaver <vincent.weaver@maine.edu> writes:
> I thought we had sorted all the AUX issues, though interestingly this is
> on a core2 system.
>
> this is:
>
> static void __rb_free_aux(struct ring_buffer *rb)
> {
>
> /*
> * Should never happen, the last reference should be dropped from
> * perf_mmap_close() path, which first stops aux transactions (which
> * in turn are the atomic holders of aux_refcount) and then does the
> * last rb_free_aux().
> */
> WARN_ON_ONCE(in_atomic());
>
>
> [87078.464463] WARNING: CPU: 1 PID: 19400 at kernel/events/ring_buffer.c:546 __rb_free_aux+0x40/0xe8
> [87078.464466] CPU: 1 PID: 19400 Comm: perf_fuzzer Tainted: G W 4.8.0+ #209
> [87078.464467] Hardware name: AOpen DE7000/nMCP7ALPx-DE R1.06 Oct.19.2012, BIOS 080015 10/19/2012
> [87078.464468] ffff88011fc85b00c ffffffff812bc679c 0000000000000000c 0000000000000000c
> [87078.464469] ffff88011fc85b40c ffffffff8104e0c8c 000002221fc85b98c ffff880119bf2700c
> [87078.464470] ffff880119bf2700c 0000000000000000c 0000000000000001c 0000000000006108c
> [87078.464470] Call Trace:
> [87078.464471] <NMI> [<ffffffff812bc679>] dump_stack+0x4d/0x63
> [87078.464472] [<ffffffff8104e0c8>] __warn+0xca/0xe5
> [87078.464473] [<ffffffff8104e19f>] warn_slowpath_null+0x1d/0x1f
> [87078.464473] [<ffffffff810fa055>] __rb_free_aux+0x40/0xe8
> [87078.464474] [<ffffffff810fab48>] rb_free_aux+0x18/0x1a
> [87078.464475] [<ffffffff810fad83>] perf_aux_output_end+0xca/0xd9
> [87078.464475] [<ffffffff81009890>] intel_bts_interrupt+0xc4/0x11f
> [87078.464476] [<ffffffff8100868c>] intel_pmu_handle_irq+0x75/0x3db
Yeah, this really shouldn't be happening. How reproducible is this? Any
clues that may help me reproduce it?
Meanwhile I'll stare at the code some more.
Regards,
--
Alex
next prev parent reply other threads:[~2016-11-10 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 4:01 Vince Weaver
2016-11-10 14:54 ` Alexander Shishkin [this message]
2016-11-10 19:58 ` Vince Weaver
2016-11-17 19:02 ` Vince Weaver
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=87a8d7o06b.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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®