From: Greg KH <gregkh@suse.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org, lwn@lwn.net,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Slaby <jirislaby@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux 2.6.32.34
Date: Wed, 23 Mar 2011 19:51:33 -0700 [thread overview]
Message-ID: <20110324025133.GA23564@suse.de> (raw)
In-Reply-To: <4D8A8DC9.1060502@suse.cz>
On Thu, Mar 24, 2011 at 01:18:17AM +0100, Jiri Slaby wrote:
> On 03/23/2011 09:34 PM, Greg KH wrote:
> > --- a/kernel/perf_event.c
> > +++ b/kernel/perf_event.c
> > @@ -4167,6 +4167,8 @@ static void tp_perf_event_destroy(struct perf_event *event)
> >
> > static const struct pmu *tp_perf_event_init(struct perf_event *event)
> > {
> > + if (event->hw.state & PERF_HES_STOPPED)
> > + return 0;
> > /*
> > * Raw tracepoint data is a severe data leak, only allow root to
> > * have these.
>
> This causes build to fail:
> /usr/src/packages/BUILD/kernel-vanilla-2.6.32.34/linux-2.6.32/kernel/perf_event.c:
> In function 'tp_perf_event_init':
> /usr/src/packages/BUILD/kernel-vanilla-2.6.32.34/linux-2.6.32/kernel/perf_event.c:4170:
> error: 'struct hw_perf_event' has no member named 'state'
> /usr/src/packages/BUILD/kernel-vanilla-2.6.32.34/linux-2.6.32/kernel/perf_event.c:4170:
> error: 'PERF_HES_STOPPED' undeclared (first use in this function)
> /usr/src/packages/BUILD/kernel-vanilla-2.6.32.34/linux-2.6.32/kernel/perf_event.c:4170:
> error: (Each undeclared identifier is reported only once
> /usr/src/packages/BUILD/kernel-vanilla-2.6.32.34/linux-2.6.32/kernel/perf_event.c:4170:
> error: for each function it appears in.)
>
>
> The source:
> commit 6f197b73304b3bd3d5a43b931383a5331d6b2987
> Author: Frederic Weisbecker <fweisbec@gmail.com>
> Date: Mon Mar 7 21:27:09 2011 +0100
>
> perf: Handle stopped state with tracepoints
>
> commit a0f7d0f7fc02465bb9758501f611f63381792996 upstream.
>
> We toggle the state from start and stop callbacks but actually
> don't check it when the event triggers. Do it so that
> these callbacks actually work.
Ick, I don't know why it builds fine here. Federic, should I just drop
this patch for the .32 tree?
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-24 2:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 20:34 Linux 2.6.32.34 Greg KH
2011-03-23 20:34 ` Greg KH
2011-03-24 0:18 ` Jiri Slaby
2011-03-24 2:51 ` Greg KH [this message]
2011-03-24 7:30 ` Ingo Molnar
2011-03-24 11:49 ` Frederic Weisbecker
2011-03-24 14:57 ` Greg KH
2011-03-24 3:39 ` Teck Choon Giam
2011-03-24 5:22 ` Mike Galbraith
2011-03-24 5:36 ` Teck Choon Giam
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=20110324025133.GA23564@suse.de \
--to=gregkh@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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