From: Mark Bloch <mbloch@nvidia.com>
To: Alex Elder <elder@linaro.org>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: quic_bjorande@quicinc.com, caleb.connolly@linaro.org,
mka@chromium.org, evgreen@chromium.org, andersson@kernel.org,
quic_cpratapa@quicinc.com, quic_avuyyuru@quicinc.com,
quic_jponduru@quicinc.com, quic_subashab@quicinc.com,
elder@kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: ipa: compute DMA pool size properly
Date: Mon, 27 Mar 2023 10:36:12 +0300 [thread overview]
Message-ID: <e5620a5a-6fdf-8254-7c42-e816e8977c1e@nvidia.com> (raw)
In-Reply-To: <20230326165223.2707557-1-elder@linaro.org>
On 26/03/2023 19:52, Alex Elder wrote:
> In gsi_trans_pool_init_dma(), the total size of a pool of memory
> used for DMA transactions is calculated. However the calculation is
> done incorrectly.
>
> For 4KB pages, this total size is currently always more than one
> page, and as a result, the calculation produces a positive (though
> incorrect) total size. The code still works in this case; we just
> end up with fewer DMA pool entries than we intended.
>
> Bjorn Andersson tested booting a kernel with 16KB pages, and hit a
> null pointer derereference in sg_alloc_append_table_from_pages(),
> descending from gsi_trans_pool_init_dma(). The cause of this was
> that a 16KB total size was going to be allocated, and with 16KB
> pages the order of that allocation is 0. The total_size calculation
> yielded 0, which eventually led to the crash.
>
> Correcting the total_size calculation fixes the problem.
>
> Reported-by: <quic_bjorande@quicinc.com>
> Tested-by: <quic_bjorande@quicinc.com>
> Fixes: 9dd441e4ed57 ("soc: qcom: ipa: GSI transactions")
> Signed-off-by: Alex Elder <elder@linaro.org>
> ---
> drivers/net/ipa/gsi_trans.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/ipa/gsi_trans.c b/drivers/net/ipa/gsi_trans.c
> index 0f52c068c46d6..ee6fb00b71eb6 100644
> --- a/drivers/net/ipa/gsi_trans.c
> +++ b/drivers/net/ipa/gsi_trans.c
> @@ -156,7 +156,7 @@ int gsi_trans_pool_init_dma(struct device *dev, struct gsi_trans_pool *pool,
> * gsi_trans_pool_exit_dma() can assume the total allocated
> * size is exactly (count * size).
> */
> - total_size = get_order(total_size) << PAGE_SHIFT;
> + total_size = PAGE_SIZE << get_order(total_size);
>
> virt = dma_alloc_coherent(dev, total_size, &addr, GFP_KERNEL);
> if (!virt)
Thanks,
Reviewed-by: Mark Bloch <mbloch@nvidia.com>
next prev parent reply other threads:[~2023-03-27 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 16:52 [PATCH net] net: ipa: compute DMA pool size properly Alex Elder
2023-03-27 7:36 ` Mark Bloch [this message]
2023-03-27 21:16 ` Bjorn Andersson
2023-03-27 23:40 ` Alex Elder
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=e5620a5a-6fdf-8254-7c42-e816e8977c1e@nvidia.com \
--to=mbloch@nvidia.com \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.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