From: sashiko-bot@kernel.org
To: "Linmao Li" <lilinmao@kylinos.cn>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (corsair-cpro) Create debugfs entries after hwmon registration
Date: Mon, 31 Aug 2026 01:51:56 +0000 [thread overview]
Message-ID: <20260831015157.1D36C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831014509.3352442-1-lilinmao@kylinos.cn>
> ccp_debugfs_init() registers debugfs files whose private data is the devm
> allocated ccp. It runs before hwmon_device_register_with_info(), so when
> that registration fails, ccp_probe() returns with the files still in
> place. The HID core then frees ccp, and ccp_remove() is not called for a
> failed probe, so nothing removes them later either. Reading one of the
> files dereferences the freed pointer.
>
> Create the debugfs entries only after the hwmon device has been
> registered, so no failing path can leave them behind.
>
> The two version queries stay where they are. They send USB commands
> without holding ccp->mutex, which is only safe as long as nothing else
> can call send_usb_cmd(); once the hwmon device is registered its
> callbacks can do so concurrently. Only the debugfs creation moves, and
> it is told which queries succeeded.
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://lore.kernel.org/linux-hwmon/20260708031612.BD7E61F000E9@smtp.kernel.org/
> Suggested-by: Guenter Roeck <linux@roeck-us.net>
> Fixes: 5997eb60f896 ("hwmon: (corsair-cpro) Add firmware and bootloader information")
> Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831014509.3352442-1-lilinmao@kylinos.cn?part=1
next prev parent reply other threads:[~2026-08-31 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 1:45 [PATCH v2] hwmon: (corsair-cpro) Create debugfs entries after hwmon registration Linmao Li
2026-08-31 1:51 ` sashiko-bot [this message]
2026-08-31 14:26 ` 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=20260831015157.1D36C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lilinmao@kylinos.cn \
--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