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 v3 0/6] firewire: core: make execution context assumptions explicit for transaction layer
Date: Mon, 12 Oct 2026 10:03:26 +0900	[thread overview]
Message-ID: <20261012010326.GA518749@sakamocchi.jp> (raw)
In-Reply-To: <20261011063146.497455-1-o-takashi@sakamocchi.jp>

On Sun, Oct 11, 2026 at 03:31:40PM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> This series is take 3 of the previous series[1].
> 
> Recent code changes have guaranteed the execution contexts of several
> functions in the transaction layer. Based on this, this series adds
> might_sleep() calls where appropriate. It also adds context analysis
> annotations and lockdep checks for several locks to document the expected
> locking context and help detect incorrect locking behavior.
> 
> Chanes from v2:
> * Switch from sparse to Compiler-based context analysis assisted by Thread
>   Safety Analysis in LLVM/Clang v23 or later.
> 
> [1][PATCH v2 0/5] firewire: core: make execution context assumptions explicit
> https://lore.kernel.org/lkml/20261009121048.282982-1-o-takashi@sakamocchi.jp/
> 
> 
> Takashi Sakamoto (6):
>   firewire: core: add might_sleep() checks to transaction layer
>   firewire: core: enable context analysis for transaction layer
>   firewire: core: use context analysis annotations and lockdep checks
>     for transactions lock
>   firewire: core: use context analysis annotations and lockdep checks
>     for split timeout lock
>   firewire: core: use context analysis annotations and lockdep checks
>     for topology map lock
>   firewire: core: narrow the card lock scope when accessing node_id
> 
>  drivers/firewire/Makefile           |  2 +
>  drivers/firewire/core-topology.c    |  3 +
>  drivers/firewire/core-transaction.c | 97 +++++++++++++++++++++++------
>  include/linux/firewire.h            | 16 ++---
>  4 files changed, 91 insertions(+), 27 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2026-10-12  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11  6:31 Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 1/6] firewire: core: add might_sleep() checks to " Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 2/6] firewire: core: enable context analysis for " Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 3/6] firewire: core: use context analysis annotations and lockdep checks for transactions lock Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 4/6] firewire: core: use context analysis annotations and lockdep checks for split timeout lock Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 5/6] firewire: core: use context analysis annotations and lockdep checks for topology map lock Takashi Sakamoto
2026-10-11  6:31 ` [PATCH v3 6/6] firewire: core: narrow the card lock scope when accessing node_id Takashi Sakamoto
2026-10-12  1:03 ` Takashi Sakamoto [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=20261012010326.GA518749@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®