From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
edmund.raile@protonmail.com, apais@linux.microsoft.com
Subject: [GIT PULL] firewire fixes for v6.17-rc1 kernel
Date: Fri, 15 Aug 2025 11:05:21 +0900 [thread overview]
Message-ID: <20250815020521.GA349651@workstation.local> (raw)
Hi Linus,
Please accept the following changes from the subsystem.
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.17-rc1
for you to fetch changes up to 0342273e14c25971f2916de2b598db2e9cfeec15:
firewire: core: reallocate buffer for FCP address handlers when more than 4 are registered (2025-08-03 21:20:15 +0900)
----------------------------------------------------------------
firewire fixes for v6.17-rc1
This set of fixes includes a solution for the issue described in the tag
annotation for v6.17 updates.
The issue involved a potential call to schedule() within an RCU read-side
critical section. The solution applies reference counting to ensure that
handlers which may call schedule() are invoked safely outside of the
critical section.
----------------------------------------------------------------
Takashi Sakamoto (4):
firewire: core: use reference counting to invoke address handlers safely
firewire: core: call handler for exclusive regions outside RCU read-side critical section
firewire: core: call FCP address handlers outside RCU read-side critical section
firewire: core: reallocate buffer for FCP address handlers when more than 4 are registered
drivers/firewire/core-transaction.c | 91 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------
include/linux/firewire.h | 4 ++++
2 files changed, 85 insertions(+), 10 deletions(-)
Regards
Takashi Sakamoto
next reply other threads:[~2025-08-15 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 2:05 Takashi Sakamoto [this message]
2025-08-15 2:30 ` [GIT PULL] firewire fixes for v6.17-rc1 kernel pr-tracker-bot
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=20250815020521.GA349651@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=apais@linux.microsoft.com \
--cc=edmund.raile@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.org \
/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