Hi,

Currently, some error paths invoke the transaction callback in the
caller's context, while a split transaction timeout invokes it from
softIRQ context. This makes the execution context of the callback
inconsistent.

This series ensures that transaction callbacks are always invoked in
process context by using a workqueue for the error paths and split
transaction timeout.


Takashi Sakamoto (3):
  firewire: core: refactor invoking transaction callback
  firewire: core: use workqueue to invoke transaction callback in some
    error cases
  firewire: core: update kerneldoc for fw_send_request() and its
    variants

 drivers/firewire/core-transaction.c | 91 +++++++++++++++--------------
 include/linux/firewire.h            | 15 +++--
 2 files changed, 56 insertions(+), 50 deletions(-)


base-commit: bbc5886fb1ee5d29438c81a770ea4bb190757b3f
-- 
2.53.0

On Mon, Sep 21, 2026 at 12:19:28PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> Currently, some error paths invoke the transaction callback in the
> caller's context, while a split transaction timeout invokes it from
> softIRQ context. This makes the execution context of the callback
> inconsistent.
> 
> This series ensures that transaction callbacks are always invoked in
> process context by using a workqueue for the error paths and split
> transaction timeout.
> 
> 
> Takashi Sakamoto (3):
>   firewire: core: refactor invoking transaction callback
>   firewire: core: use workqueue to invoke transaction callback in some
>     error cases
>   firewire: core: update kerneldoc for fw_send_request() and its
>     variants
> 
>  drivers/firewire/core-transaction.c | 91 +++++++++++++++--------------
>  include/linux/firewire.h            | 15 +++--
>  2 files changed, 56 insertions(+), 50 deletions(-)

Applied to for-next.


Regards

Takashi Sakamoto