From: Sudeep Holla <sudeep.holla@kernel.org>
To: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Cristian Marussi <cristian.marussi@arm.com>
Subject: [PATCH v2 05/14] firmware: arm_scmi: Free transport channel on IDR failure
Date: Wed, 01 Jul 2026 17:52:26 +0100 [thread overview]
Message-ID: <20260701-scmi_core_fixes-v2-5-1f5e85553f73@kernel.org> (raw)
In-Reply-To: <20260701-scmi_core_fixes-v2-0-1f5e85553f73@kernel.org>
If transport channel setup succeeds but the following IDR insertion fails,
the error path destroys the transport device and frees the channel info
without invoking the transport cleanup callback.
Call chan_free() before destroying the device so transport specific
resources such as IRQs, mailbox channels and mapped shared memory are
released consistently with the normal teardown path.
Fixes: 05a2801d8b90 ("firmware: arm_scmi: Use dedicated devices to initialize channels")
Reported-by: Sashiko <sashiko-bot@kernel.org>
Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org>
---
drivers/firmware/arm_scmi/driver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/firmware/arm_scmi/driver.c b/drivers/firmware/arm_scmi/driver.c
index 861087b2920e..4b369b003003 100644
--- a/drivers/firmware/arm_scmi/driver.c
+++ b/drivers/firmware/arm_scmi/driver.c
@@ -2808,6 +2808,7 @@ static int scmi_chan_setup(struct scmi_info *info, struct device_node *of_node,
"unable to allocate SCMI idr slot err %d\n", ret);
/* Destroy channel and device only if created by this call. */
if (tdev) {
+ info->desc->ops->chan_free(prot_id, cinfo, idr);
scmi_device_destroy(info->dev, prot_id, name);
devm_kfree(info->dev, cinfo);
}
--
2.43.0
next prev parent reply other threads:[~2026-07-01 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 16:52 [PATCH v2 00/14] firmware: arm_scmi: Fix SCMI core cleanup paths Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 01/14] firmware: arm_scmi: Fix OF node reference handling Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 02/14] firmware: arm_scmi: Fix transport device teardown lookup Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 03/14] firmware: arm_scmi: Clean up channels on setup failure Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 04/14] firmware: arm_scmi: Fix SCMI device destroy lifetimes Sudeep Holla
2026-07-01 16:52 ` Sudeep Holla [this message]
2026-07-01 16:52 ` [PATCH v2 06/14] firmware: arm_scmi: Unregister device notifier before IDR teardown Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 07/14] firmware: arm_scmi: Unwind TX receiver mailbox setup failure Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 08/14] firmware: arm_scmi: Unwind P2A " Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 09/14] firmware: arm_scmi: Protect device request lookup with RCU Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 10/14] firmware: arm_scmi: Avoid IDR updates while cleaning channels Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 11/14] firmware: arm_scmi: Clear SystemPower flag on create failure Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 12/14] firmware: arm_scmi: Reject out of range DT protocol IDs Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 13/14] firmware: arm_scmi: Stop channels before notification teardown Sudeep Holla
2026-07-01 16:52 ` [PATCH v2 14/14] firmware: arm_scmi: Publish mailbox cinfo before channel request Sudeep Holla
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=20260701-scmi_core_fixes-v2-5-1f5e85553f73@kernel.org \
--to=sudeep.holla@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.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