From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf_event: fix perf_swevent_hrtimer()
Date: Thu, 10 Dec 2009 13:24:27 +0800 [thread overview]
Message-ID: <4B20860B.6070301@cn.fujitsu.com> (raw)
In-Reply-To: <1260422135.4165.3.camel@twins>
Peter Zijlstra wrote:
> On Thu, 2009-12-10 at 12:14 +0800, Xiao Guangrong wrote:
>> fix:
>> [<c0477471>] ? printk+0x1d/0x24
>> [<c01c98f9>] ? perf_prepare_sample+0x269/0x280
>> [<c0149231>] warn_slowpath_common+0x71/0xd0
>> [<c01c98f9>] ? perf_prepare_sample+0x269/0x280
>> [<c01492aa>] warn_slowpath_null+0x1a/0x20
>> [<c01c98f9>] perf_prepare_sample+0x269/0x280
>> [<c016e9f3>] ? cpu_clock+0x53/0x90
>> [<c01cc368>] __perf_event_overflow+0x2a8/0x300
>> [<c01ccc3b>] perf_event_overflow+0x1b/0x30
>> [<c01ccccf>] perf_swevent_hrtimer+0x7f/0x120
>>
>> This is because 'data' variable not initialize.
>
> Nope, please just initialize the missing variable.
Ah, my mistake, I'll resend it.
Thanks,
Xiao
next prev parent reply other threads:[~2009-12-10 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 4:14 [PATCH] perf_event: fix perf_swevent_hrtimer() Xiao Guangrong
2009-12-10 5:15 ` Peter Zijlstra
2009-12-10 5:24 ` Xiao Guangrong [this message]
2009-12-10 6:00 ` [PATCH v2] " Xiao Guangrong
2009-12-10 6:18 ` [tip:perf/urgent] perf_event: Fix perf_swevent_hrtimer() variable initialization tip-bot for Xiao Guangrong
2009-12-10 9:08 ` [PATCH] perf_event: fix variable initialization in other path Xiao Guangrong
2009-12-10 16:24 ` [tip:perf/urgent] perf_event: Fix variable initialization in other codepaths tip-bot for Xiao Guangrong
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=4B20860B.6070301@cn.fujitsu.com \
--to=xiaoguangrong@cn.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
/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