From: Arnav Kapoor <kapoorarnav43@gmail.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] platform/x86/intel-uncore-freq: Fix error handling
Date: Mon, 16 Nov 2026 22:41:57 +0530 [thread overview]
Message-ID: <20261116171158.19754-1-kapoorarnav43@gmail.com> (raw)
In-Reply-To: <20261115014948.2517688-1-srinivas.pandruvada@linux.intel.com>
On Sat, Nov 14, 2026 at 05:49:46PM -0800, Srinivas Pandruvada wrote:
> While reviewing the driver code with AI models, identified a few corner
> cases during the device probe and removal paths where error handling and
> resource cleanup were insufficient or improperly ordered.
Tested the series on a Tiger Lake laptop (Lenovo V14 G2 ITL), which uses
the MSR based driver, so the TPMI hunk of 1/2 is not covered:
- max_freq_khz write to min_freq_khz and back
- 50 rounds of rmmod/insmod of intel-uncore-frequency while two loops
kept reading the package_00_die_00 attributes
- offlining all CPUs but CPU0 and bringing them back; the entry stayed
and current_freq_khz still read through CPU0
No hangs and nothing in dmesg.
Tested-by: Arnav Kapoor <kapoorarnav43@gmail.com>
Thanks,
Arnav
prev parent reply other threads:[~2026-11-16 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-15 1:49 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 ` [PATCH 2/2] platform/x86/intel-uncore-freq: Fix deadlock when removing attributes Srinivas Pandruvada
2026-11-16 17:11 ` Arnav Kapoor [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=20261116171158.19754-1-kapoorarnav43@gmail.com \
--to=kapoorarnav43@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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®