(subset) [PATCH v9 0/6] arm_ffa, KVM: Fix FF-A emad offset calculations

[Will Deacon]

On Tue, Jul 07, 2026 at 11:58:01AM +0100, Marc Zyngier wrote:
> On Thu, 02 Jul 2026 10:38:37 +0000, Sebastian Ene wrote:
> > This series fixes the Endpoint Memory Access Descriptor (EMAD) offset
> > calculations and adds the necessary bounds checks for both the core
> > FF-A driver and the pKVM hypervisor.
> > 
> > Prior to FF-A version 1.1, the memory region header didn't specify an
> > explicit offset for the EMADs, leading to the assumption that they
> > immediately follow the header.
> > However, from v1.1 onwards, the specification dictates using the
> > ep_mem_offset` field to determine the start of the memory access
> > array.
> > 
> > [...]
> 
> Applied to fixes, thanks!
> 
> [3/6] KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim()
>       commit: 8c6db30d79528279abbeb416e4f533f1f91b8724
> [4/6] KVM: arm64: Validate the offset to the mem access descriptor
>       commit: a6b49d27c17909608d54523220bb6f3498d4a1df
> [5/6] KVM: arm64: Ensure FFA ranges are page aligned
>       commit: 6a7a181f6921db3d9aed1bba7e15547fefd7eedc
> [6/6] KVM: arm64: Zero out the stack initialized data in the FFA handler
>       commit: 2bd3c6c702f3a9e2bcb3b536b0fbbaa645005d71

Thanks, Marc!

I think Sudeep was also happy for the driver changes to go via the KVM
tree, unless you'd prefer not to pick them up [1].

Will

[1] https://lore.kernel.org/r/20260518-heavy-intelligent-partridge-ddc80b@sudeepholla