Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932166AbbBBD46 (ORCPT ); Sun, 1 Feb 2015 22:56:58 -0500 Received: from aserp1040.oracle.com ([141.146.126.69]:51693 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932070AbbBBD44 (ORCPT ); Sun, 1 Feb 2015 22:56:56 -0500 Message-ID: <54CEF574.6040404@oracle.com> Date: Mon, 02 Feb 2015 11:56:36 +0800 From: ethan zhao Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Viresh Kumar CC: Rafael Wysocki , santosh shilimkar , Linaro Kernel Mailman List , "linux-pm@vger.kernel.org" , linux-kernel Subject: Re: [PATCH Resend] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject References: <54CEECF7.7020504@oracle.com> <54CEF123.5050106@oracle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1742 Lines: 50 On 2015/2/2 11:43, Viresh Kumar wrote: > On 2 February 2015 at 09:08, ethan zhao wrote: >>> We take cpufreq_driver_lock() here, and so this will >>> block thread B. >> No, there is no cpufreq_driver_lock acquired between >> >> cpufreq_cpu_get() and cpufreq_cpu_put() > I am not saying that the lock is taken between them. But within > cpufreq_cpu_get() to make sure policy doesn't get freed while we > are doing kobject_get(). How to prevent the policy to be freed between cpufreq_cpu_get() and cpufreq_cpu_put() ? >>>> beginning the deference of policy Thread B: >>>> ... ... __cpufreq_remove_dev_finish() >>>> cpufreq_policy_free(policy); >>>> >>>> >>>> Perhaps move policy->rwsem out side the policy structure is a way to >>>> avoid >>>> it completely. >>>> and you could stopping the PPC thread stepping forward as my patch as >>>> temporary workaround. >>> I couldn't understand your problem completely. Apart from giving a >>> detailed >>> look of what's going on both threads, always specify where the BUG >>> actually >>> is.. >> The problem is you are using a rwsem inside policy structure to protect its >> assessment, that is bad design. > What is the current bug you are facing right now, I haven't understood it well. > Also a lock within the structure isn't new. Its all over the kernel. I > don't understand > why you say its a bad design. You are maxing up the water with sand ? Thanks, Ethan > > -- > viresh -- 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/