From: Jorge Ramirez <jorge.ramirez@oss.qualcomm.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
Cc: mukesh.ojha@oss.qualcomm.com, andersson@kernel.org,
sumit.garg@oss.qualcomm.com, konradybcio@kernel.org,
harshal.dev@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom: pas_tee: handle a NULL resource table
Date: Mon, 12 Oct 2026 10:03:46 +0200 [thread overview]
Message-ID: <asyUYnlZWt-ESGut@RAMIREZO.na.qualcomm.com> (raw)
In-Reply-To: <20261006064747.2454980-1-jorge.ramirez@oss.qualcomm.com>
On 06/10/26 08:41:49, Jorge Ramirez-Ortiz wrote:
> Stopping a remote processor clears its cached resource table pointer
> but leaves the size set. On restart, qcom_pas_tee_get_rsc_table() copies
> from NULL when the firmware has no resource table:
>
> pc : __pi_memcpy_generic+0x110/0x22c
> lr : qcom_pas_tee_get_rsc_table+0xf0/0x244
>
> Zero the input size when the table is NULL so the copy is skipped.
>
> Fixes: b6f7978da0c4 ("firmware: qcom: Add a PAS TEE service")
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
> ---
> drivers/firmware/qcom/qcom_pas_tee.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/qcom/qcom_pas_tee.c b/drivers/firmware/qcom/qcom_pas_tee.c
> index ac33a00687aa..a52a7df385ff 100644
> --- a/drivers/firmware/qcom/qcom_pas_tee.c
> +++ b/drivers/firmware/qcom/qcom_pas_tee.c
> @@ -230,12 +230,15 @@ static void *qcom_pas_tee_get_rsc_table(struct device *dev,
> },
> [1] = {
> .attr = TEE_IOCTL_PARAM_ATTR_TYPE_MEMREF_INOUT,
> - .u.memref.size = input_rt_size,
> }
> };
> void *rt_buf = NULL;
> int ret;
>
> + if (!input_rt)
> + input_rt_size = 0;
> + param[1].u.memref.size = input_rt_size;
> +
> ret = tee_client_invoke_func(data->ctx, &inv_arg, param);
> if (ret < 0 || inv_arg.ret != 0) {
> dev_err(dev, "PAS get RT failed, pas_id: %d, ret: %d, err: 0x%x\n",
> --
> 2.54.0
>
could we merge this? as mentioned, it protects against blindly
dereferencin a pointer that might be null. I submitted another patch
that should address the issue in a higher level interface but regardless
I see nothing wrong with catching it here as well.
TIA
next prev parent reply other threads:[~2026-10-12 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 6:41 Jorge Ramirez-Ortiz
2026-10-12 8:03 ` Jorge Ramirez [this message]
2026-10-12 9:18 ` Sumit Garg
2026-10-12 9:57 ` Jorge Ramirez
2026-10-12 10:42 ` Sumit Garg
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=asyUYnlZWt-ESGut@RAMIREZO.na.qualcomm.com \
--to=jorge.ramirez@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=harshal.dev@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=sumit.garg@oss.qualcomm.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 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®