From: Luis Henriques <luis.henriques@canonical.com>
To: Li Zefan <lizefan@huawei.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.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: Mon, 05 Aug 2013 11:57:01 +0100 [thread overview]
Message-ID: <87fvuojthe.fsf@canonical.com> (raw)
In-Reply-To: <51FF5FC9.8080302@huawei.com> (Li Zefan's message of "Mon, 5 Aug 2013 16:18:17 +0800")
Li Zefan <lizefan@huawei.com> writes:
> 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.
>
> --
> Li Zefan
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks, I'm queuing it for the 3.5 kernel.
Cheers,
--
Luis
prev parent reply other threads:[~2013-08-05 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 8:18 stable: please queue commit 0231bb5 ("perf: Fix event group context move") Li Zefan
2013-08-05 8:21 ` Ingo Molnar
2013-08-31 20:47 ` Ben Hutchings
2013-08-05 10:57 ` Luis Henriques [this message]
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=87fvuojthe.fsf@canonical.com \
--to=luis.henriques@canonical.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.