[v1,0/3] cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev()

Message ID	5585781.DvuYhMxLoT@kreacher
Headers	show Return-Path: <linux-pm-owner@kernel.org> From: "Rafael J. Wysocki" <rjw@rjwysocki.net> To: Linux PM <linux-pm@vger.kernel.org> Cc: LKML <linux-kernel@vger.kernel.org>, Viresh Kumar <viresh.kumar@linaro.org> Subject: [PATCH v1 0/3] cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev() Date: Wed, 11 May 2022 17:46:41 +0200 Message-ID: <5585781.DvuYhMxLoT@kreacher> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Precedence: bulk
Series	cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev() \| expand [v1,0/3] cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev() [v1,1/3] cpufreq: Reorganize checks in cpufreq_offline() [v1,2/3] cpufreq: Split cpufreq_offline() [v1,3/3] cpufreq: Rearrange locking in cpufreq_remove_dev()

Message ID

5585781.DvuYhMxLoT@kreacher

Headers

From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
        Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH v1 0/3] cpufreq: Locking-related changes in cpufreq_offline()
 and cpufreq_remove_dev()
Date: Wed, 11 May 2022 17:46:41 +0200
Message-ID: <5585781.DvuYhMxLoT@kreacher>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Series

cpufreq: Locking-related changes in cpufreq_offline() and cpufreq_remove_dev() | expand

Message

Rafael J. Wysocki May 11, 2022, 3:46 p.m. UTC

Hi,

This series is based on the observation that the policy rwsem is used (or rather not
used) inconsistently in cpufreq_remove_dev() (in summary, it does things without
holding the policy rwsem that are done under that rwsem elsewhere).

The first two patches are preparatory (but patch [1/3] is a good enough improvement
by itself IMO) and patch [3/3] makes the essential change.

Please refer to the patch changelogs for details.

Thanks!