From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755170AbbDONsP (ORCPT ); Wed, 15 Apr 2015 09:48:15 -0400 Received: from mail-yh0-f50.google.com ([209.85.213.50]:36407 "EHLO mail-yh0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754281AbbDONsE (ORCPT ); Wed, 15 Apr 2015 09:48:04 -0400 Message-ID: <552E6C12.8010702@gmail.com> Date: Wed, 15 Apr 2015 07:48:02 -0600 From: David Ahern User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Peter Zijlstra , tglx@linutronix.de CC: mingo@kernel.org, linux-kernel@vger.kernel.org, Stephane Eranian Subject: Re: [PATCH 3/3] perf: Fix mux_interval hrtimer wreckage References: <20150415094155.601987867@infradead.org> <20150415095011.863052571@infradead.org> In-Reply-To: <20150415095011.863052571@infradead.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Peter: On 4/15/15 3:41 AM, Peter Zijlstra wrote: > Thomas stumbled over the hrtimer_forward_now() in > perf_event_mux_interval_ms_store() and noticed its broken-ness. > > You cannot just change the expiry time of an active timer, it will > destroy the red-black tree order and cause havoc. > > Change it to (re)start the timer instead, (re)starting a timer will > dequeue and enqueue a timer and therefore preserve rb-tree order. Should this be fixed in stable trees as well? David