From: sashiko-bot@kernel.org
To: "Sebastian Ene" <sebastianene@google.com>
Cc: "Oliver Upton" <oupton@kernel.org>,
kvmarm@lists.linux.dev, "Marc Zyngier" <maz@kernel.org>
Subject: Re: [PATCH v9 3/7] KVM: arm64: Support FFA_NOTIFICATION_UNBIND in host handler
Date: Mon, 07 Sep 2026 17:32:55 +0000 [thread overview]
Message-ID: <20260907173256.495A51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907171930.4037166-4-sebastianene@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] do_ffa_notif_unbind improperly restricts the host to only unbind notifications where it is the receiver, preventing it from unbinding notifications it sent.
--
commit c6b253b0c883368d7d43d8e94ff20acf54cb8109
Author: Sebastian Ene <sebastianene@google.com>
KVM: arm64: Support FFA_NOTIFICATION_UNBIND in host handler
This commit adds support for the FFA_NOTIFICATION_UNBIND hypercall in the
host handler, verifying arguments and forwarding the message to Trustzone.
> diff --git a/arch/arm64/kvm/hyp/nvhe/ffa.c b/arch/arm64/kvm/hyp/nvhe/ffa.c
> index 89872e12f9d45..a1ba4463d1ef7 100644
> --- a/arch/arm64/kvm/hyp/nvhe/ffa.c
> +++ b/arch/arm64/kvm/hyp/nvhe/ffa.c
[ ... ]
> @@ -913,6 +912,27 @@ static void do_ffa_notif_bind(struct arm_smccc_1_2_regs *res,
> hyp_smccc_1_2_smc(args, res);
> }
>
> +static void do_ffa_notif_unbind(struct arm_smccc_1_2_regs *res,
> + struct kvm_cpu_context *ctxt)
> +{
> + DECLARE_REG(u32, endp_id, ctxt, 1);
> + DECLARE_REG(u32, reserved, ctxt, 2);
> + struct arm_smccc_1_2_regs *args;
> +
> + if (reserved) {
> + ffa_to_smccc_res(res, FFA_RET_INVALID_PARAMETERS);
> + return;
> + }
> +
> + if (FIELD_GET(FFA_NOTIF_RECEIVER_ENDP_MASK, endp_id) != HOST_FFA_ID) {
> + ffa_to_smccc_res(res, FFA_RET_INVALID_PARAMETERS);
> + return;
> + }
[Severity: Medium]
Does this check improperly restrict the host to only unbind notifications
where it is the receiver?
The FF-A 1.1 specification explicitly permits either the sender or receiver
to unbind a notification. By unconditionally rejecting the hypercall when
the receiver ID does not match HOST_FFA_ID, this prevents the host (acting
as a sender) from unbinding a notification it bound to an SP.
> +
> + args = (void *)&ctxt->regs.regs[0];
> + hyp_smccc_1_2_smc(args, res);
> +}
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260907171930.4037166-1-sebastianene@google.com?part=3
next prev parent reply other threads:[~2026-09-07 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 17:19 [PATCH v9 0/7] KVM: arm64: Forward FFA_NOTIFICATION* calls to TrustZone Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 1/7] KVM: arm64: Forward FFA_NOTIFICATION_BITMAP calls to Trustzone Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 2/7] KVM: arm64: Support FFA_NOTIFICATION_BIND in host handler Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 3/7] KVM: arm64: Support FFA_NOTIFICATION_UNBIND " Sebastian Ene
2026-09-07 17:32 ` sashiko-bot [this message]
2026-09-07 17:19 ` [PATCH v9 4/7] KVM: arm64: Support FFA_NOTIFICATION_SET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 5/7] KVM: arm64: Support FFA_NOTIFICATION_GET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 6/7] KVM: arm64: Support FFA_NOTIFICATION_INFO_GET " Sebastian Ene
2026-09-07 17:19 ` [PATCH v9 7/7] KVM: arm64: Enforce strict SBZ checks in the FF-A proxy Sebastian Ene
2026-09-07 17:33 ` sashiko-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=20260907173256.495A51F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sebastianene@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.