mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] firewire: core: use spinlock_irqsave() appropriately for transaction list lock
Date: Fri, 9 Oct 2026 09:22:16 +0900	[thread overview]
Message-ID: <20261009002216.GA258845@sakamocchi.jp> (raw)
In-Reply-To: <20261008234432.251412-2-o-takashi@sakamocchi.jp>

On Fri, Oct 09, 2026 at 08:44:27AM +0900, Takashi Sakamoto wrote:
> The transaction.lock in the fw_card structure protects the transaction
> list from concurrent access. The list is mostly accessed from process
> context, with two exceptions: split_transaction_timeout_callback()
> acquires the lock in softIRQ context for the timer wheel, and
> __fw_send_request() acquires it in the caller's context, which can
> include hardIRQ context.
> 
> Use spinlock_irq() in process context and spinlock_irqsave() in the other
> contexts. Update the relevant scoped_guard() invocations accordingly and
> remove the unnecessary comments.
> 
> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
> ---
>  drivers/firewire/core-transaction.c | 27 +++++----------------------
>  1 file changed, 5 insertions(+), 22 deletions(-)

I realized that the change is incorrect in the way to use these spin_lock
variants. Drop this from the series.


Regards

Takashi Sakamoto

  reply	other threads:[~2026-10-09  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 23:44 [PATCH 0/6] firewire: core: make execution context assumptions explicit Takashi Sakamoto
2026-10-08 23:44 ` [PATCH 1/6] firewire: core: use spinlock_irqsave() appropriately for transaction list lock Takashi Sakamoto
2026-10-09  0:22   ` Takashi Sakamoto [this message]
2026-10-08 23:44 ` [PATCH 2/6] firewire: core: add might_sleep() checks Takashi Sakamoto
2026-10-08 23:44 ` [PATCH 3/6] firewire: core: use sparse annotations and lockdep checks for transaction lock Takashi Sakamoto
2026-10-08 23:44 ` [PATCH 4/6] firewire: core: use sparse annotations and lockdep checks for topology map lock Takashi Sakamoto
2026-10-08 23:44 ` [PATCH 5/6] firewire: core: use sparse annotations and lockdep checks for split timeout lock Takashi Sakamoto
2026-10-08 23:44 ` [PATCH 6/6] firewire: core: narrow the card lock scope when accessing node_id Takashi Sakamoto

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=20261009002216.GA258845@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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®