From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: hansg@kernel.org, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [PATCH 2/2] platform/x86/intel-uncore-freq: Fix deadlock when removing attributes
Date: Sat, 14 Nov 2026 17:49:48 -0800 [thread overview]
Message-ID: <20261115014948.2517688-3-srinivas.pandruvada@linux.intel.com> (raw)
In-Reply-To: <20261115014948.2517688-1-srinivas.pandruvada@linux.intel.com>
uncore_freq_remove_die_entry() holds uncore_lock while removing the
attribute group of an entry. Removing attributes waits for active sysfs
callbacks of these attributes to finish. But the show and store callbacks
take uncore_lock, which results in an ABBA deadlock:
CPU0 CPU1
---- ----
kernfs_fop_read_iter()
show_attr() uncore_freq_remove_die_entry()
mutex_lock(&uncore_lock)
mutex_lock(&uncore_lock) delete_attr_group()
sysfs_remove_group()
waits for CPU0
Mark the entry as not valid with an invalid control CPU under
uncore_lock, and remove the attribute group after releasing it. Free
the seqnum_id after the attribute group is removed, so that the name
can't be used by a new entry while the old attributes still exist.
Adding and removing the same entry is serialized by the callers: CPU
hotplug callbacks in the MSR based driver, and device probe and remove
in the TPMI driver. Callbacks running before the attributes are removed
are safe: the MSR based driver returns -ENXIO for an invalid control CPU,
and the TPMI driver MMIO is unmapped only after the device is removed.
Fixes: ae7b2ce57851 ("platform/x86/intel/uncore-freq: Use sysfs API to create attributes")
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
.../uncore-frequency-common.c | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.c b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.c
index 6051aa040abf..22019099a857 100644
--- a/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.c
+++ b/drivers/platform/x86/intel/uncore-frequency/uncore-frequency-common.c
@@ -313,17 +313,24 @@ void uncore_freq_remove_die_entry(struct uncore_data *data)
{
mutex_lock(&uncore_lock);
/* Nothing to remove, if the entry was not added or already removed */
- if (!data->valid)
- goto uncore_unlock;
+ if (!data->valid) {
+ mutex_unlock(&uncore_lock);
+ return;
+ }
- delete_attr_group(data, data->name);
data->control_cpu = -1;
data->valid = false;
+ mutex_unlock(&uncore_lock);
+
+ /*
+ * Removing the attributes waits for active sysfs callbacks, which take
+ * uncore_lock. So this can't be done while holding uncore_lock.
+ */
+ delete_attr_group(data, data->name);
+
+ /* Free the ID after the attributes with the name using it are removed */
if (data->domain_id != UNCORE_DOMAIN_ID_INVALID)
ida_free(&intel_uncore_ida, data->seqnum_id);
-
-uncore_unlock:
- mutex_unlock(&uncore_lock);
}
EXPORT_SYMBOL_NS_GPL(uncore_freq_remove_die_entry, "INTEL_UNCORE_FREQUENCY");
--
2.55.0
prev parent reply other threads:[~2026-11-15 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 1:49 [PATCH 0/2] platform/x86/intel-uncore-freq: Fix error handling Srinivas Pandruvada
2026-11-15 1:49 ` [PATCH 1/2] platform/x86/intel-uncore-freq: Don't remove entries which are not added Srinivas Pandruvada
2026-11-15 1:49 ` Srinivas Pandruvada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261115014948.2517688-3-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®