From: Wilken Gottwalt <wilken.gottwalt@posteo.net>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] hwmon: (corsair-psu) Close HID device on probe errors
Date: Fri, 24 Apr 2026 15:37:35 +0000 [thread overview]
Message-ID: <20260424173734.4ab5765f@posteo.net> (raw)
In-Reply-To: <20260424135107.13720-1-mhun512@gmail.com>
On Fri, 24 Apr 2026 22:50:51 +0900
Myeonghun Pak <mhun512@gmail.com> wrote:
> corsairpsu_probe() opens the HID device before sending the device init
> and firmware-info commands. If either command fails, the error path jumps
> directly to fail_and_stop and skips hid_hw_close().
>
> Use the existing fail_and_close label for those post-open failures so the
> open count and low-level close callback are balanced before hid_hw_stop().
>
> Fixes: d115b51e0e56 ("hwmon: add Corsair PSU HID controller driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> ---
> drivers/hwmon/corsair-psu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hwmon/corsair-psu.c b/drivers/hwmon/corsair-psu.c
> index dddbd2463f..76f3e1da68 100644
> --- a/drivers/hwmon/corsair-psu.c
> +++ b/drivers/hwmon/corsair-psu.c
> @@ -796,13 +796,13 @@ static int corsairpsu_probe(struct hid_device *hdev, const struct
> hid_device_id ret = corsairpsu_init(priv);
> if (ret < 0) {
> dev_err(&hdev->dev, "unable to initialize device (%d)\n", ret);
> - goto fail_and_stop;
> + goto fail_and_close;
> }
>
> ret = corsairpsu_fwinfo(priv);
> if (ret < 0) {
> dev_err(&hdev->dev, "unable to query firmware (%d)\n", ret);
> - goto fail_and_stop;
> + goto fail_and_close;
> }
>
> corsairpsu_get_criticals(priv);
I really had to go back to the initial commit to check, if I introduced that
issue later. But nope, I had it that way from the start. Good catch, I totally
missed that. Thank you.
greetings,
Wilken
Reviewed-by: Wilken Gottwalt <wilken.gottwalt@posteo.net>
next prev parent reply other threads:[~2026-04-24 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 13:50 [PATCH] hwmon: (corsair-psu) Close HID device on probe errors Myeonghun Pak
2026-04-24 14:21 ` sashiko-bot
2026-04-24 15:37 ` Wilken Gottwalt [this message]
2026-04-30 18:20 ` Guenter Roeck
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=20260424173734.4ab5765f@posteo.net \
--to=wilken.gottwalt@posteo.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mhun512@gmail.com \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.