From: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
To: Peng Fan <peng.fan@oss.nxp.com>,
<linux-remoteproc@vger.kernel.org>, <agross@kernel.org>,
<andersson@kernel.org>, <lgirdwood@gmail.com>,
<broonie@kernel.org>, <robh+dt@kernel.org>,
<quic_plai@quicinc.com>, <bgoswami@quicinc.com>, <perex@perex.cz>,
<tiwai@suse.com>, <srinivas.kandagatla@linaro.org>,
<quic_rohkumar@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <swboyd@chromium.org>,
<judyhsiao@chromium.org>, <devicetree@vger.kernel.org>,
<krzysztof.kozlowski@linaro.org>, <mathieu.poirier@linaro.org>
Subject: Re: [PATCH] remoteproc: elf_loader: Update resource table name check
Date: Mon, 12 Dec 2022 19:57:59 +0530 [thread overview]
Message-ID: <bbd462ec-33ed-1302-6532-8efb1af91017@quicinc.com> (raw)
In-Reply-To: <24361a63-ee96-4291-175e-f25c1380cd49@oss.nxp.com>
On 12/10/2022 8:36 AM, Peng Fan wrote:
Thanks for your time and valuable suggestion Pang!!!
>
> On 12/1/2022 8:20 PM, Srinivasa Rao Mandadapu wrote:
>> Update resource table name check with sub string search instead of
>> complete string search.
>> In general Qualcomm binary contains, section header name
>> (e.g. .resource_table), amended with extra string to differentiate
>> with other sections.
>> So far Android adsp binaries are being authenticated using TZ,
>> hence this mismatch hasn't created any problem.
>> In recent developments, ADSP binary is being used in Chrome based
>> platforms, which doesn't have TZ path, hence resource table is
>> required for memory sandboxing.
>>
>> Signed-off-by: Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
>> ---
>> drivers/remoteproc/remoteproc_elf_loader.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/remoteproc/remoteproc_elf_loader.c
>> b/drivers/remoteproc/remoteproc_elf_loader.c
>> index 5a412d7..0feb120 100644
>> --- a/drivers/remoteproc/remoteproc_elf_loader.c
>> +++ b/drivers/remoteproc/remoteproc_elf_loader.c
>> @@ -272,7 +272,7 @@ find_table(struct device *dev, const struct
>> firmware *fw)
>> u64 offset = elf_shdr_get_sh_offset(class, shdr);
>> u32 name = elf_shdr_get_sh_name(class, shdr);
>> - if (strcmp(name_table + name, ".resource_table"))
>> + if (!strstr(name_table + name, ".resource_table"))
>> continue;
>
> How about ?
> if (strcmp(name_table + name, ".resource_table")) {
> if (strstr(name_table + name, ".resource_table"))
> break;
> continue;
> }
It looks valid approach to me. But other reviewers may object on double
check. Let's see Stephen Boyd comments also,
and handle it accordingly.
>
> Regards,
> Peng.
>> table = (struct resource_table *)(elf_data + offset);
prev parent reply other threads:[~2022-12-12 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 12:20 Srinivasa Rao Mandadapu
2022-12-07 1:55 ` Stephen Boyd
2022-12-08 13:40 ` Srinivasa Rao Mandadapu
2022-12-09 20:52 ` Stephen Boyd
2022-12-12 13:49 ` Srinivasa Rao Mandadapu
2022-12-12 19:04 ` Stephen Boyd
2022-12-10 3:06 ` Peng Fan
2022-12-12 14:27 ` Srinivasa Rao Mandadapu [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=bbd462ec-33ed-1302-6532-8efb1af91017@quicinc.com \
--to=quic_srivasam@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=judyhsiao@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.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=peng.fan@oss.nxp.com \
--cc=perex@perex.cz \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.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®