Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932417AbbBBEGW (ORCPT ); Sun, 1 Feb 2015 23:06:22 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:38308 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754773AbbBBEGU (ORCPT ); Sun, 1 Feb 2015 23:06:20 -0500 Message-ID: <54CEF7AA.80401@oracle.com> Date: Mon, 02 Feb 2015 12:06:02 +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> <54CEF574.6040404@oracle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1084 Lines: 35 On 2015/2/2 11:59, Viresh Kumar wrote: > On 2 February 2015 at 09:26, ethan zhao wrote: >> How to prevent the policy to be freed between >> >> cpufreq_cpu_get() and cpufreq_cpu_put() ? > kobject_get() increases the reference count of a policy and the policy > will only be freed when this is zero. And it will only be zero once all > cpufreq_cpu_get() are matched with corresponding cpufreq_cpu_put(). Is that an idea it supposed to be or fact ? if (!cpufreq_suspended) cpufreq_policy_free(policy); static void cpufreq_policy_free(struct cpufreq_policy *policy) { free_cpumask_var(policy->related_cpus); free_cpumask_var(policy->cpus); kfree(policy); } It seems you just think about it ideally in mind. Thanks, Ethan > >> You are maxing up the water with sand ? > :) -- 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/