Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751809AbaGaQSP (ORCPT ); Thu, 31 Jul 2014 12:18:15 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:63164 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750774AbaGaQSO (ORCPT ); Thu, 31 Jul 2014 12:18:14 -0400 From: "Rafael J. Wysocki" To: Prarit Bhargava Cc: Saravana Kannan , linux-kernel@vger.kernel.org, Viresh Kumar , Lenny Szubowicz , linux-pm@vger.kernel.org Subject: Re: [PATCH] cpufreq, store_scaling_governor requires policy->rwsem to be held for duration of changing governors [v2] Date: Thu, 31 Jul 2014 18:36:47 +0200 Message-ID: <2066166.pXm4lKLOID@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <53DA1916.4090806@redhat.com> References: <1406634362-811-1-git-send-email-prarit@redhat.com> <3140593.vs3eOK6CdF@vostro.rjw.lan> <53DA1916.4090806@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, July 31, 2014 06:23:18 AM Prarit Bhargava wrote: > > On 07/30/2014 10:16 PM, Rafael J. Wysocki wrote: > > On Wednesday, July 30, 2014 06:36:00 PM Saravana Kannan wrote: > >> On 07/30/2014 02:40 PM, Rafael J. Wysocki wrote: > >>> On Wednesday, July 30, 2014 10:18:25 AM Prarit Bhargava wrote: > >>>> > >>>> On 07/29/2014 08:03 PM, Rafael J. Wysocki wrote: > >>>>> On Tuesday, July 29, 2014 07:46:02 AM Prarit Bhargava wrote: > >>> > >>> [cut] > >>> > >>>>>> This patch effectively reverts commit 955ef483. > >> > >> The issue reported in this patch is valid. We are seeing that internally > >> too. I believe I reported it in another thread (within the past month). > >> > >> However, the original patch fixes a real deadlock issue (I'm too tired > >> to look it up now). We can revet the original, but it's going to bring > >> back the original issue. I just want to make sure Prarit and Raphael > >> realize this before proceeding. > >> > >> I do have plans for a proper fix for the mainline (not stable branches), > >> but plan to do that after the current set of suspend/hotplug patches go > >> through. The fix would be easier to make after that. > >> > >>>>> > >>>>> OK, I'm convinced by this. > >>>>> > >>>>> I suppose we should push it for -stable from 3.10 through 3.15.x, right? > >>>> > >>>> Rafael, I think that is a good idea. I'm not sure what the protocol is for > >>>> adding stable@kernel.org though ... > > Rafael, let me (again) re-write the patch description. I think Saravana has > raised an important issue that I have not clearly identified why it is safe to > remove this code in my patch description. Also, I want to clearly identify the > appropriate -stable releases to push this out to. > > I'll submit a [v3] later today or tomorrow. In any case that's too late for 3.16 final, unless there's an -rc8. Thanks for doing that work! Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/