aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com
diff options
context:
space:
mode:
authorSudeep Holla <sudeep.holla@kernel.org>2026-04-28 19:33:31 +0100
committerSudeep Holla <sudeep.holla@kernel.org>2026-05-05 16:42:48 +0100
commit2af18f8e36b277730527cacc2256b1332f56aa28 (patch)
tree60d01488e7c79e6c2ae13c97bd0061525a136541 /tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com
parentfirmware: arm_ffa: Bound PARTITION_INFO_GET_REGS copies (diff)
firmware: arm_ffa: Keep framework RX release under lock
The framework notification handler drops rx_lock before issuing FFA_RX_RELEASE, leaving a window where another RX-buffer user can start a new FF-A transaction before ownership has actually been returned to firmware. Move the FFA_RX_RELEASE calls so they execute while rx_lock is still held on both the kmemdup() failure path and the normal success path. While doing that, switch the handler to scoped_guard() to keep the critical section explicit. Fixes: 285a5ea0f542 ("firmware: arm_ffa: Add support for handling framework notifications") Link: https://patch.msgid.link/20260428-ffa_fixes-v2-7-8595ae450034@kernel.org Signed-off-by: Sudeep Holla <sudeep.holla@kernel.org>
Diffstat (limited to 'tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions