From: Andre Przywara <andre.przywara@arm.com>
To: Nirmoy Das <nirmoyd@nvidia.com>,
Salman Nabi <salman.nabi@arm.com>,
vvidwans@nvidia.com, sudeep.holla@arm.com, mark.rutland@arm.com,
lpieralisi@kernel.org
Cc: ardb@kernel.org, chao.gao@intel.com,
linux-arm-kernel@lists.infradead.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org, sdonthineni@nvidia.com,
vsethi@nvidia.com, vwadekar@nvidia.com
Subject: Re: [PATCH 1/1] firmware: smccc: add support for Live Firmware Activation (LFA)
Date: Fri, 13 Mar 2026 15:39:48 +0100 [thread overview]
Message-ID: <1e233b43-0118-435e-a9df-29a535d63740@arm.com> (raw)
In-Reply-To: <19aeb934-7e36-4f30-8f7f-a8ae74a797f5@nvidia.com>
Hi Nirmoy,
On 3/13/26 10:46, Nirmoy Das wrote:
> Hi Salman and Andre,
>
>
> We found an bug while testing LFA. See below:
>
> On 19.01.26 14:27, Salman Nabi wrote:
>> The Arm Live Firmware Activation (LFA) is a specification [1] to describe
>> activating firmware components without a reboot. Those components
>> (like TF-A's BL31, EDK-II, TF-RMM, secure paylods) would be updated the
>> usual way: via fwupd, FF-A or other secure storage methods, or via some
>> IMPDEF Out-Of-Bound method. The user can then activate this new firmware,
>> at system runtime, without requiring a reboot.
>> The specification covers the SMCCC interface to list and query available
>> components and eventually trigger the activation.
[ .... ]
>> +
>> + update_fw_images_tree();
>> +
>> + /*
>> + * Removing non-valid image directories at the end of an activation.
>> + * We can't remove the sysfs attributes while in the respective
>> + * _store() handler, so have to postpone the list removal to a
>> + * workqueue.
>> + */
>> + INIT_WORK(&fw_images_update_work, remove_invalid_fw_images);
>
>
> This can get invoke multiple times so re-initializing a work item that
> may already be queued or running
>
> is unsafe. This should be moved to lfa_init() so it is only called once.
> I suggest:
Ah, good point, thanks for spotting and reporting. Will fold this into
the next post!
Cheers,
Andre
>
> diff --git a/drivers/firmware/smccc/lfa_fw.c b/drivers/firmware/smccc/
> lfa_fw.c
> index 90727a66e49a5..135358113104c 100644
> --- a/drivers/firmware/smccc/lfa_fw.c
> +++ b/drivers/firmware/smccc/lfa_fw.c
> @@ -653,7 +653,6 @@ static int update_fw_images_tree(void)
> * _store() handler, so have to postpone the list removal to a
> * workqueue.
> */
> - INIT_WORK(&fw_images_update_work, remove_invalid_fw_images);
> queue_work(fw_images_update_wq, &fw_images_update_work);
>
> return 0;
> @@ -680,7 +679,7 @@ static void lfa_notify_handler(acpi_handle handle,
> u32 event, void *data)
> * of all activable and pending images.
> */
> do {
> - /* Reset activable image flag */
> + flush_workqueue(fw_images_update_wq);
> found_activable_image = false;
> list_for_each_entry(attrs, &lfa_fw_images, image_node) {
> if (attrs->fw_seq_id == -1)
> @@ -782,6 +781,8 @@ static int __init lfa_init(void)
> return -ENOMEM;
> }
>
> + INIT_WORK(&fw_images_update_work, remove_invalid_fw_images);
> +
> pr_info("Live Firmware Activation: detected v%ld.%ld\n",
> reg.a0 >> 16, reg.a0 & 0xffff);
>
>
> Regards,
>
> Nirmoy
>
>> + queue_work(fw_images_update_wq, &fw_images_update_work);
>> + mutex_unlock(&lfa_lock);
>> +
>> + return ret;
>> +}
>> +
prev parent reply other threads:[~2026-03-13 14:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 12:27 [PATCH 0/1] Arm Live Firmware Activation (LFA) support Salman Nabi
2026-01-19 12:27 ` [PATCH 1/1] firmware: smccc: add support for Live Firmware Activation (LFA) Salman Nabi
2026-01-19 16:29 ` kernel test robot
2026-01-19 16:41 ` Andre Przywara
2026-01-19 18:41 ` kernel test robot
2026-01-19 21:35 ` kernel test robot
2026-01-27 23:01 ` Vedashree Vidwans
2026-01-29 17:26 ` Andre Przywara
2026-01-30 19:29 ` Vedashree Vidwans
2026-01-30 20:31 ` Andre Przywara
2026-01-31 1:35 ` Trilok Soni
2026-02-02 15:52 ` Salman Nabi
2026-02-06 6:37 ` Trilok Soni
2026-02-10 22:20 ` Vedashree Vidwans
2026-02-20 17:39 ` Andre Przywara
2026-02-20 21:48 ` Trilok Soni
2026-03-13 9:46 ` Nirmoy Das
2026-03-13 14:39 ` Andre Przywara [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=1e233b43-0118-435e-a9df-29a535d63740@arm.com \
--to=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=chao.gao@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=nirmoyd@nvidia.com \
--cc=salman.nabi@arm.com \
--cc=sdonthineni@nvidia.com \
--cc=sudeep.holla@arm.com \
--cc=vsethi@nvidia.com \
--cc=vvidwans@nvidia.com \
--cc=vwadekar@nvidia.com \
/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
all inboxes | Powered by JetHome®