From: sashiko-bot@kernel.org
To: "Eugene Shalygin" <eugene.shalygin@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (asus-ec-sensors) add missed handle for ENOMEM
Date: Sun, 12 Jul 2026 12:58:06 +0000 [thread overview]
Message-ID: <20260712125807.242661F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260712125147.1254339-1-eugene.shalygin@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The newly added error handling incorrectly returns `status` (which evaluates to 0) instead of the actual error code when `asus_ec_hwmon_add_chan_info()` fails.
--
--- Patch [1]: [PATCH] hwmon: (asus-ec-sensors) add missed handle for ENOMEM ---
commit 2fb0c06e28b3b0aad223266de4f30ef04ff0537b
Author: Eugene Shalygin <eugene.shalygin@gmail.com>
hwmon: (asus-ec-sensors) add missed handle for ENOMEM
This commit adds a missing return value check in the setup function
asus_ec_probe() to handle potential memory allocation failures.
> diff --git a/drivers/hwmon/asus-ec-sensors.c b/drivers/hwmon/asus-ec-sensors.c
> index 29a23484cbe7b..dd8c1a3f182e3 100644
> --- a/drivers/hwmon/asus-ec-sensors.c
> +++ b/drivers/hwmon/asus-ec-sensors.c
> @@ -1495,9 +1495,10 @@ static int asus_ec_probe(struct platform_device *pdev)
> if (!nr_count[type])
> continue;
>
> - asus_ec_hwmon_add_chan_info(asus_ec_hwmon_chan, dev,
> - nr_count[type], type,
> - hwmon_attributes[type]);
> + if (asus_ec_hwmon_add_chan_info(asus_ec_hwmon_chan, dev,
> + nr_count[type], type,
> + hwmon_attributes[type]))
> + return status;
[Severity: High]
Does this correctly return the error code? At this point in asus_ec_probe(),
status appears to be 0 from the earlier successful call to setup_lock_data().
Should this capture and return the actual error code from
asus_ec_hwmon_add_chan_info() instead, to avoid returning success (0) while
aborting the probe?
> *ptr_asus_ec_ci++ = asus_ec_hwmon_chan++;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260712125147.1254339-1-eugene.shalygin@gmail.com?part=1
prev parent reply other threads:[~2026-07-12 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 12:51 [PATCH] hwmon: (asus-ec-sensors) add missed handle for ENOMEM Eugene Shalygin
2026-07-12 12:58 ` sashiko-bot [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=20260712125807.242661F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eugene.shalygin@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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