From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
mukesh.ojha@oss.qualcomm.com, sumit.garg@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remoteproc: qcom: pas: pass no resource table when the firmware has none
Date: Fri, 16 Oct 2026 13:06:48 +0200 [thread overview]
Message-ID: <cd2318b8-7619-4885-bde7-5ec6961ac5fa@oss.qualcomm.com> (raw)
In-Reply-To: <20261005125411.2151326-1-jorge.ramirez@oss.qualcomm.com>
On 10/5/26 2:54 PM, Jorge Ramirez-Ortiz wrote:
> The firmware resource table is passed to the PAS backend even when the
> firmware carries none. This only works on the first boot, while the
> cached pointer and its size are both zero.
>
> Stopping the remote processor, or failing to start it, frees the cached
> table and clears the pointer but leaves the size set. The next start
> then pairs a NULL table with a non-zero size.
>
> The SCM backend substitutes an empty table and hides the problem. The
> TEE backend copies from the NULL pointer:
>
> remoteproc remoteproc2: powering up cdsp
> pc : __pi_memcpy_generic+0x110/0x22c
> lr : qcom_pas_tee_get_rsc_table+0xf4/0x25c
> Call trace:
> __pi_memcpy_generic+0x110/0x22c (P)
> qcom_pas_get_rsc_table+0x38/0x60
> qcom_pas_parse_firmware+0xa0/0x100
> rproc_boot+0x2d4/0x380
> state_store+0x40/0x100
>
> Fixes: a4584bff63c8 ("remoteproc: pas: Extend parse_fw callback to fetch resources via SMC call")
> Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez@oss.qualcomm.com>
> ---
To my understanding, this patch is right
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
As an additional safeguard, we should probably drop the stale table
size whenever the pointer is reset to null:
diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
--- a/drivers/remoteproc/remoteproc_core.c
+++ b/drivers/remoteproc/remoteproc_core.c
@@
clean_up_resources:
rproc_resource_cleanup(rproc);
kfree(rproc->cached_table);
rproc->cached_table = NULL;
rproc->table_ptr = NULL;
+ rproc->table_sz = 0;
unprepare_rproc:
@@
kfree(rproc->cached_table);
rproc->cached_table = NULL;
rproc->table_ptr = NULL;
+ rproc->table_sz = 0;
return rproc_attach(rproc);
@@
kfree(rproc->cached_table);
rproc->cached_table = NULL;
rproc->table_ptr = NULL;
+ rproc->table_sz = 0;
out:
@@
kfree(rproc->cached_table);
rproc->cached_table = NULL;
rproc->table_ptr = NULL;
+ rproc->table_sz = 0;
out:
Konrad
prev parent reply other threads:[~2026-10-16 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 12:54 Jorge Ramirez-Ortiz
2026-10-05 16:12 ` Mukesh Ojha
2026-10-05 21:01 ` Jorge Ramirez
2026-10-06 5:23 ` Harshal Dev
2026-10-06 6:54 ` Jorge Ramirez
2026-10-06 10:03 ` Mukesh Ojha
2026-10-10 11:25 ` Sumit Garg
2026-10-13 10:06 ` Mukesh Ojha
2026-10-16 11:06 ` Konrad Dybcio [this message]
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=cd2318b8-7619-4885-bde7-5ec6961ac5fa@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=jorge.ramirez@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=sumit.garg@kernel.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
all inboxes | Powered by JetHome®