From: Ben Hutchings <ben@decadent.org.uk>
To: Ingo Molnar <mingo@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: stable: please queue commit 0231bb5 ("perf: Fix event group context move")
Date: Sat, 31 Aug 2013 21:47:29 +0100 [thread overview]
Message-ID: <1377982049.9792.44.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <20130805082118.GD26746@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
On Mon, 2013-08-05 at 10:21 +0200, Ingo Molnar wrote:
> * Li Zefan <lizefan@huawei.com> wrote:
>
> > Plese consider adding commit 0231bb5336758426b44ccd798ccd3c5419c95d58
> > to stable tree. It fixes a real bug, which was explained here:
> >
> > http://thread.gmane.org/gmane.linux.kernel.perf.user/1144
> >
> > and I've managed to reproduce the bug in 3.4 kernel with the test
> > program attached in the above email, and I've confirmed the bug fix.
> >
> > The effect of the bug is, if we open a group of mixed events(sw/hw)
> > and the "disabled" flag is not set and sw events come first, then
> > some of the perf events won't be started after the call to perf_event_open().
> >
> > The bug fix should be applicable to kernels >= 3.0 && <= 3.7.
>
> Acked-by: Ingo Molnar <mingo@kernel.org>
Queued up for 3.2, thanks.
Ben.
--
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-08-31 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 8:18 Li Zefan
2013-08-05 8:21 ` Ingo Molnar
2013-08-31 20:47 ` Ben Hutchings [this message]
2013-08-05 10:57 ` Luis Henriques
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=1377982049.9792.44.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®