Skip to contentSkip to conversation

firmware: arm_ffa: Unmap Rx/Tx buffers on shutdown

PATCH In review Carol L Soto 2 participants 5 messages Aug 18 – Sep 1 Firmware framework for ARMV8-a

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 firmware: arm_ffa: Unmap Rx/Tx buffers on shutdown

The FF-A core maps its Rx/Tx buffers with the firmware during probe, but only unmaps them from the remove and probe error paths. A kexec reboot runs device_shutdown() without removing the driver, leaving the old buffers mapped in the firmware.

The next kernel can then fail to register its Rx/Tx buffers because the firmware still tracks the previous mapping.

Add a platform shutdown callback and share the firmware cleanup path with remove and probe error handling so FF-A partitions, notifications and the Rx/Tx buffer mapping are torn down before entering the next kernel.

Fixes 3bbfe9871005 ("firmware: arm_ffa: Add initial Arm FFA driver support")
---
 drivers/firmware/arm_ffa/driver.c | 52 ++++++++++++++++++++++++++-----
 1 file changed, 44 insertions(+), 8 deletions(-)
drivers/firmware/arm_ffa/driver.c +44 -8
index 8654b3365c9b..c94a6eabe4bc 100644
@@ -119,6 +119,8 @@ struct ffa_drv_info {
 	struct xarray partition_info;
 	DECLARE_HASHTABLE(notifier_hash, ilog2(FFA_MAX_NOTIFICATIONS));
 	rwlock_t notify_lock; /* lock to protect notifier hashtable  */
+	bool rxtx_mapped;
+	bool partitions_setup;
 };
 
 static struct ffa_drv_info *drv_info;
@@ -2109,6 +2111,36 @@ static void ffa_notifications_setup(void)
 	ffa_notifications_cleanup();
 }
 
+static void ffa_fw_cleanup(struct ffa_drv_info *info)
+{
+	if (info->partitions_setup) {
+		ffa_partitions_cleanup();
+		info->partitions_setup = false;
+	}
+
+	ffa_notifications_cleanup();
+
+	if (info->rxtx_mapped) {
+		ffa_rxtx_unmap();
+		info->rxtx_mapped = false;
+	}
+}
+
+static void ffa_shutdown(struct platform_device *pdev)
+{
+	struct ffa_drv_info *info = platform_get_drvdata(pdev);
+
+	if (!info)
+		return;
+
+	/*
+	 * FF-A devices are children of the core platform device, so their
+	 * shutdown callbacks have already run. Drop the FF-A devices and
+	 * global firmware state before kexec enters the next kernel.
+	 */
+	ffa_fw_cleanup(info);
+}
+
 static int ffa_probe(struct platform_device *pdev)
 {
 	int ret;
@@ -2183,6 +2215,7 @@ static int ffa_probe(struct platform_device *pdev)
 	}
 	drv_info->rxtx_bufsz = rxtx_bufsz;
 
+	drv_info->rxtx_mapped = true;
 	mutex_init(&drv_info->rx_lock);
 	mutex_init(&drv_info->tx_lock);
 
@@ -2191,12 +2224,16 @@ static int ffa_probe(struct platform_device *pdev)
 	ffa_notifications_setup();
 
 	ret = ffa_setup_partitions();
-	if (!ret)
-		return ret;
+	if (ret) {
+		pr_err("failed to setup partitions\n");
+		goto fw_cleanup;
+	}
+	drv_info->partitions_setup = true;
 
-	pr_err("failed to setup partitions\n");
-	ffa_notifications_cleanup();
-	ffa_rxtx_unmap();
+	return 0;
+
+fw_cleanup:
+	ffa_fw_cleanup(drv_info);
 free_pages:
 	if (drv_info->tx_buffer)
 		free_pages_exact(drv_info->tx_buffer, rxtx_bufsz);
@@ -2212,9 +2249,7 @@ static void ffa_remove(struct platform_device *pdev)
 {
 	struct ffa_drv_info *info = platform_get_drvdata(pdev);
 
-	ffa_notifications_cleanup();
-	ffa_partitions_cleanup();
-	ffa_rxtx_unmap();
+	ffa_fw_cleanup(info);
 	free_pages_exact(info->tx_buffer, info->rxtx_bufsz);
 	free_pages_exact(info->rx_buffer, info->rxtx_bufsz);
 	kfree(info);
@@ -2225,6 +2260,7 @@ static void ffa_remove(struct platform_device *pdev)
 static struct platform_driver ffa_driver = {
 	.probe = ffa_probe,
 	.remove = ffa_remove,
+	.shutdown = ffa_shutdown,
 	.driver = {
 		.name = FFA_PLATFORM_NAME,
 	},
Signature · 1 line
2.25.1
maintainer
#1 lore raw
Quoted 8 lines · Carol L Soto

The FF-A core maps its Rx/Tx buffers with the firmware during probe, but only unmaps them from the remove and probe error paths. A kexec reboot runs device_shutdown() without removing the driver, leaving the old buffers mapped in the firmware.

The next kernel can then fail to register its Rx/Tx buffers because the firmware still tracks the previous mapping.

I had posted a single line patch here[1]. The original author/reported never got back.

Signature · 4 lines
Regards,
Sudeep

[1] https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla
author
#2 lore raw
Quoted 5 lines · Sudeep Holla

I had posted a single line patch here[1]. The original author/reported never got back.

-- Regards, Sudeep [1]
https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla

Hi Sudeep,

Thanks for the pointer. I tried your patch from [1] and it fixes the kexec issue on my setup.

I also tried limiting the shutdown patch to just RXTX_UNMAP, but that is not sufficient here. The next kernel can still fail notificaion setup with:

ARM FF-A: Notification bitmap create error -13

So I agree that using the normal FF-A cleanup patch from shutdown looks like the right approach, since it tears down the notification bitmap state as well as unmapping the Rx/Tx buffers.

Are you planning to submit that change to resolve this issue?

Thanks,
Carol

author
#3 lore raw
Quoted 17 lines · Carol Soto
Quoted 5 lines · Sudeep Holla

I had posted a single line patch here[1]. The original author/reported never got back.

-- Regards, Sudeep [1]
https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla

Hi Sudeep,

Thanks for the pointer. I tried your patch from [1] and it fixes the kexec issue on my setup.

I also tried limiting the shutdown patch to just RXTX_UNMAP, but that is not sufficient here. The next kernel can still fail notificaion setup with:

ARM FF-A: Notification bitmap create error -13

Quoted 7 lines

So I agree that using the normal FF-A cleanup patch from shutdown looks like the right approach, since it tears down the notification bitmap state as well as unmapping the Rx/Tx buffers.

Are you planning to submit that change to resolve this issue?

Thanks,
Carol

Hi Suddep,

Just following up on the FF-A kexec issue. Do you plan to submit your shutdown cleanup patch, or would you prefer that I send a v2 based on that approach?

Thanks,

Carol

maintainer
#4 lore raw
Quoted 28 lines · Carol Soto
Quoted 26 lines · Carol Soto
Quoted 5 lines · Sudeep Holla

I had posted a single line patch here[1]. The original author/reported never
got back.

-- Regards, Sudeep [1] https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla

Hi Sudeep,

Thanks for the pointer. I tried your patch from [1] and it fixes the kexec issue on my setup.

I also tried limiting the shutdown patch to just RXTX_UNMAP, but that is not sufficient here.
The next kernel can still fail notificaion setup with:

ARM FF-A: Notification bitmap create error -13

So I agree that using the normal FF-A cleanup patch from shutdown looks like the right approach,
since it tears down the notification bitmap state as well as unmapping the Rx/Tx buffers.

Are you planning to submit that change to resolve this issue?

Quoted 9 lines
Quoted 2 lines

Thanks,
Carol

Hi Suddep,

Just following up on the FF-A kexec issue. Do you plan to submit your shutdown cleanup patch, or would you prefer that I send a v2 based on that approach?

I was away for a while, I will post it as a proper patch soon. Sorry for the delay.

Signature · 2 lines
Regards,
Sudeep