From a3c69f14de97758decdc4364cb5d89f8ea9923e9 Mon Sep 17 00:00:00 2001 From: Takashi Sakamoto Date: Tue, 15 Sep 2026 07:14:34 +0900 Subject: firewire: core: correct comment about execution context The comment for fw_address_callback_t describes the execution context, but the callback has not been called from RCU read-side critical section since v6.17. Fixes: e884a8a0c573 ("firewire: core: call FCP address handlers outside RCU read-side critical section") Fixes: e8cf6875005b ("firewire: core: call handler for exclusive regions outside RCU read-side critical section") Link: https://lore.kernel.org/r/20260914221434.213633-1-o-takashi@sakamocchi.jp Signed-off-by: Takashi Sakamoto --- include/linux/firewire.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'include/linux') diff --git a/include/linux/firewire.h b/include/linux/firewire.h index a1e0cb4526c9..cbe59a18162e 100644 --- a/include/linux/firewire.h +++ b/include/linux/firewire.h @@ -299,8 +299,9 @@ union fw_transaction_callback { }; /* - * This callback handles an inbound request subaction. It is called in - * RCU read-side context, therefore must not sleep. + * This callback handles an inbound request subaction. If the request subaction is initiated from + * the local node (e.g. by unit driver), the execution context depends on the initiator and is + * unspecified. Otherwise, it runs in workqueue context. * * The callback should not initiate outbound request subactions directly. * Otherwise there is a danger of recursion of inbound and outbound -- cgit v1.2.3