From: Robin Murphy <robin.murphy@arm.com>
To: Sibi Sankar <quic_sibis@quicinc.com>,
andersson@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, manivannan.sadhasivam@linaro.org
Cc: agross@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
konrad.dybcio@somainline.org, amit.pundir@linaro.org,
regressions@leemhuis.info, sumit.semwal@linaro.org,
will@kernel.org, catalin.marinas@arm.com
Subject: Re: [PATCH 4/4] remoteproc: qcom_q6v5_mss: Use a carveout to authenticate modem headers
Date: Tue, 13 Dec 2022 15:07:46 +0000 [thread overview]
Message-ID: <741b64c2-0b09-6475-5736-d2cd3e33c34c@arm.com> (raw)
In-Reply-To: <20221213140724.8612-5-quic_sibis@quicinc.com>
On 2022-12-13 14:07, Sibi Sankar wrote:
> The memory region allocated using dma_alloc_attr with no kernel mapping
> attribute set would still be a part of the linear kernel map. Any access
> to this region by the application processor after assigning it to the
> remote Q6 will result in a XPU violation. Fix this by replacing the
> dynamically allocated memory region with a no-map carveout and unmap the
> modem metadata memory region before passing control to the remote Q6.
>
> Reported-by: Amit Pundir <amit.pundir@linaro.org>
> Fixes: 6c5a9dc2481b ("remoteproc: qcom: Make secure world call for mem ownership switch")
> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
> ---
>
> The addition of the carveout and memunmap is required only on SoCs that
> mandate memory protection before transferring control to Q6, hence the
> driver falls back to dynamic memory allocation in the absence of the
> modem metadata carveout.
The DMA_ATTR_NO_KERNEL_MAPPING stuff is still broken and pointless, so
I'd expect to see this solution replacing it, not being added alongside.
It's just silly to say pass the "I don't need a CPU mapping" flag, then
manually open-code the same CPU mapping you would have got if you
hadn't, in a way that only works at all when a cacheable alias exists
anyway.
Thanks,
Robin.
> drivers/remoteproc/qcom_q6v5_mss.c | 85 +++++++++++++++++++++---------
> 1 file changed, 61 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/remoteproc/qcom_q6v5_mss.c b/drivers/remoteproc/qcom_q6v5_mss.c
> index fddb63cffee0..8264275ecbd0 100644
> --- a/drivers/remoteproc/qcom_q6v5_mss.c
> +++ b/drivers/remoteproc/qcom_q6v5_mss.c
> @@ -211,6 +211,7 @@ struct q6v5 {
> size_t mba_size;
> size_t dp_size;
>
> + phys_addr_t mdata_phys;
> phys_addr_t mpss_phys;
> phys_addr_t mpss_reloc;
> size_t mpss_size;
> @@ -935,6 +936,7 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc, const struct firmware *fw,
> {
> unsigned long dma_attrs = DMA_ATTR_FORCE_CONTIGUOUS | DMA_ATTR_NO_KERNEL_MAPPING;
> unsigned long flags = VM_DMA_COHERENT | VM_FLUSH_RESET_PERMS;
> + void *mdata_region;
> struct page **pages;
> struct page *page;
> dma_addr_t phys;
> @@ -951,34 +953,48 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc, const struct firmware *fw,
> if (IS_ERR(metadata))
> return PTR_ERR(metadata);
>
> - page = dma_alloc_attrs(qproc->dev, size, &phys, GFP_KERNEL, dma_attrs);
> - if (!page) {
> - kfree(metadata);
> - dev_err(qproc->dev, "failed to allocate mdt buffer\n");
> - return -ENOMEM;
> - }
> + if (qproc->mdata_phys) {
> + mdata_region = memremap(qproc->mdata_phys, size, MEMREMAP_WC);
> + if (!mdata_region) {
> + dev_err(qproc->dev, "unable to map memory region: %pa+%zx\n",
> + &qproc->mdata_phys, size);
> + ret = -EBUSY;
> + goto free_dma_attrs;
> + }
>
> - count = PAGE_ALIGN(size) >> PAGE_SHIFT;
> - pages = kmalloc_array(count, sizeof(struct page *), GFP_KERNEL);
> - if (!pages) {
> - ret = -ENOMEM;
> - goto free_dma_attrs;
> - }
> + memcpy(mdata_region, metadata, size);
> + memunmap(mdata_region);
> + phys = qproc->mdata_phys;
> + } else {
> + page = dma_alloc_attrs(qproc->dev, size, &phys, GFP_KERNEL, dma_attrs);
> + if (!page) {
> + kfree(metadata);
> + dev_err(qproc->dev, "failed to allocate mdt buffer\n");
> + return -ENOMEM;
> + }
>
> - for (i = 0; i < count; i++)
> - pages[i] = nth_page(page, i);
> + count = PAGE_ALIGN(size) >> PAGE_SHIFT;
> + pages = kmalloc_array(count, sizeof(struct page *), GFP_KERNEL);
> + if (!pages) {
> + ret = -ENOMEM;
> + goto free_dma_attrs;
> + }
>
> - vaddr = vmap(pages, count, flags, pgprot_dmacoherent(PAGE_KERNEL));
> - kfree(pages);
> - if (!vaddr) {
> - dev_err(qproc->dev, "unable to map memory region: %pa+%zx\n", &phys, size);
> - ret = -EBUSY;
> - goto free_dma_attrs;
> - }
> + for (i = 0; i < count; i++)
> + pages[i] = nth_page(page, i);
>
> - memcpy(vaddr, metadata, size);
> + vaddr = vmap(pages, count, flags, pgprot_dmacoherent(PAGE_KERNEL));
> + kfree(pages);
> + if (!vaddr) {
> + dev_err(qproc->dev, "unable to map memory region: %pa+%zx\n", &phys, size);
> + ret = -EBUSY;
> + goto free_dma_attrs;
> + }
>
> - vunmap(vaddr);
> + memcpy(vaddr, metadata, size);
> +
> + vunmap(vaddr);
> + }
>
> /* Hypervisor mapping to access metadata by modem */
> mdata_perm = BIT(QCOM_SCM_VMID_HLOS);
> @@ -1008,7 +1024,8 @@ static int q6v5_mpss_init_image(struct q6v5 *qproc, const struct firmware *fw,
> "mdt buffer not reclaimed system may become unstable\n");
>
> free_dma_attrs:
> - dma_free_attrs(qproc->dev, size, page, phys, dma_attrs);
> + if (!qproc->mdata_phys)
> + dma_free_attrs(qproc->dev, size, page, phys, dma_attrs);
> kfree(metadata);
>
> return ret < 0 ? ret : 0;
> @@ -1882,6 +1899,26 @@ static int q6v5_alloc_memory_region(struct q6v5 *qproc)
> qproc->mpss_phys = qproc->mpss_reloc = r.start;
> qproc->mpss_size = resource_size(&r);
>
> + if (!child) {
> + node = of_parse_phandle(qproc->dev->of_node, "memory-region", 2);
> + } else {
> + child = of_get_child_by_name(qproc->dev->of_node, "metadata");
> + node = of_parse_phandle(child, "memory-region", 0);
> + of_node_put(child);
> + }
> +
> + if (!node)
> + return 0;
> +
> + ret = of_address_to_resource(node, 0, &r);
> + of_node_put(node);
> + if (ret) {
> + dev_err(qproc->dev, "unable to resolve metadata region\n");
> + return ret;
> + }
> +
> + qproc->mdata_phys = r.start;
> +
> return 0;
> }
>
next prev parent reply other threads:[~2022-12-13 15:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 14:07 [PATCH 0/4] Fix XPU violation during modem metadata authentication Sibi Sankar
2022-12-13 14:07 ` [PATCH 1/4] arm64: dts: qcom: Introduce a carveout for modem metadata Sibi Sankar
2022-12-13 19:40 ` Krzysztof Kozlowski
2022-12-14 6:49 ` Sibi Sankar
2022-12-14 8:09 ` Krzysztof Kozlowski
2022-12-14 11:27 ` Krzysztof Kozlowski
2022-12-14 11:44 ` Sibi Sankar
2022-12-14 12:54 ` Krzysztof Kozlowski
2022-12-13 14:07 ` [PATCH 2/4] dt-bindings: remoteproc: qcom: sc7180: Update memory-region requirements Sibi Sankar
2022-12-13 19:41 ` Krzysztof Kozlowski
2022-12-14 10:25 ` Sibi Sankar
2022-12-14 11:30 ` Krzysztof Kozlowski
2022-12-14 11:56 ` Sibi Sankar
2022-12-13 14:07 ` [PATCH 3/4] dt-bindings: remoteproc: qcom: q6v5: Update memory region requirements Sibi Sankar
2022-12-13 14:07 ` [PATCH 4/4] remoteproc: qcom_q6v5_mss: Use a carveout to authenticate modem headers Sibi Sankar
2022-12-13 15:07 ` Robin Murphy [this message]
2022-12-13 15:57 ` Sibi Sankar
2022-12-13 16:07 ` Manivannan Sadhasivam
2022-12-14 12:49 ` Robin Murphy
2022-12-13 19:47 ` Krzysztof Kozlowski
2022-12-14 10:33 ` Sibi Sankar
2022-12-14 11:28 ` Krzysztof Kozlowski
2022-12-14 11:51 ` Sibi Sankar
2022-12-15 8:51 ` Krzysztof Kozlowski
2022-12-27 12:18 ` [PATCH 0/4] Fix XPU violation during modem metadata authentication Amit Pundir
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=741b64c2-0b09-6475-5736-d2cd3e33c34c@arm.com \
--to=robin.murphy@arm.com \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_sibis@quicinc.com \
--cc=regressions@leemhuis.info \
--cc=robh+dt@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).