From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kurt Borja <kuurtb@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>, Armin Wolf <W_Armin@gmx.de>,
Mario Limonciello <mario.limonciello@amd.com>,
platform-driver-x86@vger.kernel.org,
Dell.Client.Kernel@dell.com, LKML <linux-kernel@vger.kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] platform/x86: alienware-wmi-wmax: Fix uninitialized variable due to bad error handling
Date: Thu, 17 Apr 2025 13:57:19 +0300 (EEST) [thread overview]
Message-ID: <14424f02-c800-a482-4d23-fd05f61cec82@linux.intel.com> (raw)
In-Reply-To: <20250416-smatch-fix-v1-1-35491b462d8f@gmail.com>
On Wed, 16 Apr 2025, Kurt Borja wrote:
> wmax_thermal_information() may also return -ENOMSG, which would leave
> `id` uninitialized in thermal_profile_probe.
>
> Reorder and modify logic to catch all errors.
>
> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> Closes: https://lore.kernel.org/r/Z_-KVqNbD9ygvE2X@stanley.mountain
> Fixes: 27e9e6339896 ("platform/x86: alienware-wmi: Refactor thermal control methods")
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
> Hi all,
>
> @Ilpo: This will definitely conflict with the for-next branch when
> merging.
Okay, thanks for the heads up (I'll eventually merge fixes into for-next
once I merge this fix).
> Also, the fixes tag references a commit from before the split (same
> series though), but ofc this fix is meant to be applied on top of it
> (fixes branch). Is this ok or would it be better to change the fixes
> tag to the "split" commit?
Pointing to the correct commit is preferred.
It doesn't look very likely that the series would be "split" such that
only a part of it appears in a specific stable kernel so the difference
shouldn't matter anyway.
In general, stable people would just send you a notification if something
cannot be backported to some stable version due to a conflict, and they'd
depend on you to submit the amended backport anyway so it's not much extra
"work" for them if something ends up conflicting. (And I don't think your
inbox would be exactly filling from stable notifications unlike mine ---
one of those joys of being a subsystem maintainer).
--
i.
> ---
> drivers/platform/x86/dell/alienware-wmi-wmax.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/platform/x86/dell/alienware-wmi-wmax.c b/drivers/platform/x86/dell/alienware-wmi-wmax.c
> index 3d3014b5adf046c94c1ebf39a0e28a92622b40d6..b8e71f06fdde347573bff5c27a9ba53a0efcacae 100644
> --- a/drivers/platform/x86/dell/alienware-wmi-wmax.c
> +++ b/drivers/platform/x86/dell/alienware-wmi-wmax.c
> @@ -607,12 +607,10 @@ static int thermal_profile_probe(void *drvdata, unsigned long *choices)
> for (u32 i = 0; i < sys_desc[3]; i++) {
> ret = wmax_thermal_information(priv->wdev, WMAX_OPERATION_LIST_IDS,
> i + first_mode, &out_data);
> -
> - if (ret == -EIO)
> - return ret;
> -
> if (ret == -EBADRQC)
> break;
> + if (ret)
> + return ret;
>
> if (!is_wmax_thermal_code(out_data))
> continue;
>
> ---
> base-commit: fcf27a6a926fd9eeba39e9c3fde43c9298fe284e
> change-id: 20250416-smatch-fix-d1191e2514f5
>
> Best regards,
>
next prev parent reply other threads:[~2025-04-17 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 16:50 [PATCH] platform/x86: alienware-wmi-wmax: Fix uninitialized variable due to bad error handling Kurt Borja
2025-04-17 10:57 ` Ilpo Järvinen [this message]
2025-04-17 20:27 ` Kurt Borja
2025-04-17 11:18 ` Ilpo Järvinen
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=14424f02-c800-a482-4d23-fd05f61cec82@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=dan.carpenter@linaro.org \
--cc=hdegoede@redhat.com \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--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