From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, jolsa@redhat.com,
sqazi@google.com, ak@linux.intel.com
Subject: Re: [PATCH] perf,x86: fix uninitialized pt_regs in intel_pmu_drain_bts_buffer()
Date: Tue, 19 Mar 2013 13:43:04 +0100 [thread overview]
Message-ID: <1363696984.22553.41.camel@laptop> (raw)
In-Reply-To: <20130318134645.GA3278@quad>
On Mon, 2013-03-18 at 14:46 +0100, Stephane Eranian wrote:
>
> This patch fixes an uninitialized pt_regs struct in drain BTS
> function. The pt_regs struct is propagated all the way to the
> code_get_segment() function from perf_instruction_pointer()
> and may get garbage.
>
> We cannot simply inherit the actual pt_regs from the interrupt
> because BTS must be flushed on context-switch or when the associated
> event is disabled. And there we do not have a pt_regs handy.
>
> Setting pt_regs to all zeroes may not be the best option but it is
> not clear what else to do given where the drain_bts_buffer() is called
> from.
>
> Signed-off-by: Stephane Eranian <eranian@google.com>
> ---
>
> diff --git a/arch/x86/kernel/cpu/perf_event_intel_ds.c b/arch/x86/kernel/cpu/perf_event_intel_ds.c
> index b05a575..208f0c8 100644
> --- a/arch/x86/kernel/cpu/perf_event_intel_ds.c
> +++ b/arch/x86/kernel/cpu/perf_event_intel_ds.c
> @@ -302,6 +302,8 @@ int intel_pmu_drain_bts_buffer(void)
> struct perf_sample_data data;
> struct pt_regs regs;
>
> + memset(®s, 0, sizeof(regs));
> +
> if (!event)
> return 0;
>
Should we not replace:
regs.ip = 0;
with that memset? It avoids the memset work in a few cases and removes
the then superfluous clearing of the IP field.
next prev parent reply other threads:[~2013-03-19 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 13:46 [PATCH] perf,x86: fix uninitialized pt_regs in intel_pmu_drain_bts_buffer() Stephane Eranian
2013-03-19 12:43 ` Peter Zijlstra [this message]
2013-03-19 12:50 ` Stephane Eranian
2013-03-19 12:58 ` Peter Zijlstra
2013-03-19 13:02 ` Stephane Eranian
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=1363696984.22553.41.camel@laptop \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sqazi@google.com \
/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