From: Purva Yeshi <purvayeshi550@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: irenic.rajneesh@gmail.com, david.e.box@intel.com,
Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: intel_pmc_core: Fix uninitialized pmc/map in pmc_core_send_ltr_ignore
Date: Fri, 18 Apr 2025 14:36:53 +0530 [thread overview]
Message-ID: <309074de-9f12-45c9-8eec-8a116ee6abf8@gmail.com> (raw)
In-Reply-To: <2b6412f7-28d7-e7c4-6c61-aac9be6dd84c@linux.intel.com>
On 17/04/25 18:43, Ilpo Järvinen wrote:
> On Thu, 17 Apr 2025, Purva Yeshi wrote:
>
>> Fix Smatch-detected issue:
>>
>> drivers/platform/x86/intel/pmc/core.c:501 pmc_core_send_ltr_ignore()
>> error: uninitialized symbol 'pmc'.
>>
>> drivers/platform/x86/intel/pmc/core.c:501 pmc_core_send_ltr_ignore()
>> error: uninitialized symbol 'map'.
>>
>> drivers/platform/x86/intel/pmc/core.c:501 pmc_core_send_ltr_ignore()
>> error: we previously assumed 'pmc' could be null (see line 479)
>>
>>
>> Prevents uninitialized symbol warnings detected by smatch.
>>
>> Ensures map is not accessed if pmc is NULL, preventing dereferencing
>> of uninitialized pointers
>>
>> Add defensive check for pmc and map to catch any unexpected edge cases
>> and ensure all required pointers are valid.
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>> ---
>> drivers/platform/x86/intel/pmc/core.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/platform/x86/intel/pmc/core.c b/drivers/platform/x86/intel/pmc/core.c
>> index 7a1d11f2914f..e674b940e29e 100644
>> --- a/drivers/platform/x86/intel/pmc/core.c
>> +++ b/drivers/platform/x86/intel/pmc/core.c
>> @@ -462,8 +462,8 @@ DEFINE_SHOW_ATTRIBUTE(pmc_core_pll);
>>
>> int pmc_core_send_ltr_ignore(struct pmc_dev *pmcdev, u32 value, int ignore)
>> {
>> - struct pmc *pmc;
>> - const struct pmc_reg_map *map;
>> + struct pmc *pmc = NULL;
>> + const struct pmc_reg_map *map = NULL;
>> u32 reg;
>> unsigned int pmc_index;
>> int ltr_index;
>> @@ -480,6 +480,9 @@ int pmc_core_send_ltr_ignore(struct pmc_dev *pmcdev, u32 value, int ignore)
>> continue;
>>
>> map = pmc->map;
>> + if (!map)
>> + continue;
>
> How can this happen?? If pmc is created, it should have a valid ->map
> AFAICT. Did you even read that code at all???
Hi,
Thanks for the feedback.
Yes, I did read through the code and I understand your point.
The motivation behind the patch was a Smatch warning about possible
uninitialized use of map and pmc, even though they are logically
guarded. I now see that these checks may not be necessary given the
existing control flow.
>
>> +
>> if (ltr_index <= map->ltr_ignore_max)
>> break;
>>
>> @@ -491,7 +494,7 @@ int pmc_core_send_ltr_ignore(struct pmc_dev *pmcdev, u32 value, int ignore)
>> ltr_index = ltr_index - (map->ltr_ignore_max + 2) - 1;
>> }
>>
>> - if (pmc_index >= ARRAY_SIZE(pmcdev->pmcs) || ltr_index < 0)
>> + if (pmc_index >= ARRAY_SIZE(pmcdev->pmcs) || ltr_index < 0 || !pmc || !map)
>
> What are the situations pmc_index >= ARRAY_SIZE(pmcdev->pmcs) check
> didn't catch where these new checks do something useful??
>
> Lots of noise but little real substance in this patch?
You're right, if pmc is non-NULL, then map should also be valid, and the
bounds check on pmc_index already prevents out-of-bounds access. Adding
further checks might just add noise.
I'll drop the patch unless there's a cleaner way to restructure the
logic to make Smatch silence without redundant checks.
Thanks again for the clarification!
Best regards,
Purva
>
prev parent reply other threads:[~2025-04-18 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 7:52 [PATCH] platform/x86: intel_pmc_core: Fix uninitialized pmc/map in pmc_core_send_ltr_ignore Purva Yeshi
2025-04-17 13:13 ` Ilpo Järvinen
2025-04-18 9:06 ` Purva Yeshi [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=309074de-9f12-45c9-8eec-8a116ee6abf8@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=david.e.box@intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=irenic.rajneesh@gmail.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