From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] firewire: core: make execution context assumptions explicit
Date: Sat, 10 Oct 2026 10:29:25 +0900 [thread overview]
Message-ID: <20261010012925.GA300419@sakamocchi.jp> (raw)
In-Reply-To: <20261009121048.282982-1-o-takashi@sakamocchi.jp>
Hi,
On Fri, Oct 09, 2026 at 09:10:43PM +0900, Takashi Sakamoto wrote:
> Hi,
>
> This series is take 2 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 sparse annotations
> and lockdep checks for several locks to document the expected locking
> context and help detect incorrect locking behavior.
>
> Chanes from v1:
> * drop a patch to arrange spinlock usages for reconsideration
>
> [1] https://lore.kernel.org/lkml/20261008234432.251412-1-o-takashi@sakamocchi.jp/
>
>
> Takashi Sakamoto (5):
> firewire: core: add might_sleep() checks
> firewire: core: use sparse annotations and lockdep checks for
> transaction lock
> firewire: core: use sparse annotations and lockdep checks for topology
> map lock
> firewire: core: use sparse annotations and lockdep checks for split
> timeout lock
> firewire: core: narrow the card lock scope when accessing node_id
>
> drivers/firewire/core-topology.c | 3 ++
> drivers/firewire/core-transaction.c | 70 ++++++++++++++++++++++++++---
> 2 files changed, 66 insertions(+), 7 deletions(-)
I realized that Sparse nowadays seems to be excluded from in-kernel
context analysis[1]. Clang took over this function with more sophisticated
features.
Let me work for refining this series with Compiler-based Context
Analysis[2].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5b63d0ae94cc
[2] https://docs.kernel.org/dev-tools/context-analysis.html
Regards
Takashi Sakamoto
prev parent reply other threads:[~2026-10-10 1:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 12:10 Takashi Sakamoto
2026-10-09 12:10 ` [PATCH v2 1/5] firewire: core: add might_sleep() checks Takashi Sakamoto
2026-10-09 12:10 ` [PATCH v2 2/5] firewire: core: use sparse annotations and lockdep checks for transaction lock Takashi Sakamoto
2026-10-09 12:10 ` [PATCH v2 3/5] firewire: core: use sparse annotations and lockdep checks for topology map lock Takashi Sakamoto
2026-10-09 12:10 ` [PATCH v2 4/5] firewire: core: use sparse annotations and lockdep checks for split timeout lock Takashi Sakamoto
2026-10-09 12:10 ` [PATCH v2 5/5] firewire: core: narrow the card lock scope when accessing node_id Takashi Sakamoto
2026-10-10 1:29 ` 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=20261010012925.GA300419@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®