Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] net: ipa: leak of PAS metadata buffer in ipa_firmware_load()
--

commit e29d8ec88fcd553654746e0eff27a3767cbabafc
Author: Mukesh Ojha <[email protected]>

net: ipa: migrate firmware loading to qcom_mdt_pas_load() and 
qcom_pas_prepare_and_auth_reset()

This commit replaces the open-coded memremap(), qcom_mdt_load(), and
qcom_pas_auth_and_reset() sequence in ipa_firmware_load() with
qcom_pas_context_init(), qcom_mdt_pas_load(), and
qcom_pas_prepare_and_auth_reset().

> diff --git a/drivers/net/ipa/ipa_main.c b/drivers/net/ipa/ipa_main.c
> index 14ac2d2faf7c2..0a37741c22858 100644
> --- a/drivers/net/ipa/ipa_main.c
> +++ b/drivers/net/ipa/ipa_main.c
> @@ -585,12 +585,11 @@ static void ipa_deconfig(struct ipa *ipa)
>  
>  static int ipa_firmware_load(struct device *dev)
>  {
> +     struct qcom_pas_context ctx;
>       const struct firmware *fw;
>       struct resource res;
>       phys_addr_t phys;
>       const char *path;
> -     ssize_t size;
> -     void *virt;
>       int ret;
>  
>       ret = of_reserved_mem_region_to_resource(dev->of_node, 0, &res);
> @@ -615,24 +614,18 @@ static int ipa_firmware_load(struct device *dev)
>       }
>  
>       phys = res.start;
> -     size = (size_t)resource_size(&res);
> -     virt = memremap(phys, size, MEMREMAP_WC);
> -     if (!virt) {
> -             dev_err(dev, "unable to remap firmware memory\n");
> -             ret = -ENOMEM;
> -             goto out_release_firmware;
> -     }
> +     qcom_pas_context_init(&ctx, dev, IPA_PAS_ID, phys, resource_size(&res));
>  
> -     ret = qcom_mdt_load(dev, fw, path, IPA_PAS_ID, virt, phys, size, NULL);
> +     ret = qcom_mdt_pas_load(&ctx, fw, path, NULL);
>       if (ret) {
>               dev_err(dev, "error %d loading \"%s\"\n", ret, path);
> -     } else {
> -             ret = qcom_pas_auth_and_reset(IPA_PAS_ID);
> -             if (ret)
> -                     dev_err(dev, "error %d authenticating \"%s\"\n", ret, 
> path);
> +             goto out_release_firmware;
>       }
>  
> -     memunmap(virt);
> +     ret = qcom_pas_prepare_and_auth_reset(&ctx);
> +     if (ret)
> +             dev_err(dev, "error %d authenticating \"%s\"\n", ret, path);
> +
>  out_release_firmware:
>       release_firmware(fw);

[Severity: Medium]
Does this leak the metadata buffer stored in ctx.ptr when
ipa_firmware_load() returns?

Previously, qcom_mdt_load() passed a NULL context to
__qcom_mdt_pas_init(), so qcom_pas_init_image() freed the metadata buffer
immediately.  qcom_mdt_pas_load() instead passes &ctx to
__qcom_mdt_pas_init() -> qcom_pas_init_image(), which retains the coherent
DMA or TEE shared-memory allocation in ctx.ptr until
qcom_pas_metadata_release(&ctx) is called.  Because ipa_firmware_load()
never calls qcom_pas_metadata_release(&ctx), the metadata buffer is leaked
on both the normal path and if qcom_mdt_pas_load() fails after
qcom_pas_init_image() succeeds.

-- 
Sashiko AI review ยท 
https://sashiko.dev/#/patchset/[email protected]?part=6

Reply via email to