From: Lizhi Hou <lizhi.hou@amd.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>, <quic_carlv@quicinc.com>,
<quic_thanson@quicinc.com>
Cc: <ogabbay@kernel.org>, <jacek.lawrynowicz@linux.intel.com>,
<dri-devel@lists.freedesktop.org>,
<linux-arm-msm@vger.kernel.org>,
"Jeffrey Hugo" <quic_jhugo@quicinc.com>
Subject: Re: [PATCH] accel/qaic: Fix possible data corruption in BOs > 2G
Date: Thu, 6 Mar 2025 09:51:39 -0800 [thread overview]
Message-ID: <554638b5-314b-b0cc-5b91-2cc635f78f7d@amd.com> (raw)
In-Reply-To: <20250306171959.853466-1-jeff.hugo@oss.qualcomm.com>
On 3/6/25 09:19, Jeff Hugo wrote:
> From: Jeffrey Hugo <quic_jhugo@quicinc.com>
>
> When slicing a BO, we need to iterate through the BO's sgt to find the
> right pieces to construct the slice. Some of the data types chosen for
> this process are incorrectly too small, and can overflow. This can
> result in the incorrect slice construction, which can lead to data
> corruption in workload execution.
>
> The device can only handle 32-bit sized transfers, and the scatterlist
> struct only supports 32-bit buffer sizes, so our upper limit for an
> individual transfer is an unsigned int. Using an int is incorrect due to
> the reservation of the sign bit. Upgrade the length of a scatterlist
> entry and the offsets into a scatterlist entry to unsigned int for a
> correct representation.
>
> While each transfer may be limited to 32-bits, the overall BO may exceed
> that size. For counting the total length of the BO, we need a type that
> can represent the largest allocation possible on the system. That is the
> definition of size_t, so use it.
>
> Fixes: ff13be830333 ("accel/qaic: Add datapath")
> Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
> Signed-off-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
> ---
> drivers/accel/qaic/qaic_data.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/accel/qaic/qaic_data.c b/drivers/accel/qaic/qaic_data.c
> index c20eb63750f5..ffcdf5738d09 100644
> --- a/drivers/accel/qaic/qaic_data.c
> +++ b/drivers/accel/qaic/qaic_data.c
> @@ -172,9 +172,10 @@ static void free_slice(struct kref *kref)
> static int clone_range_of_sgt_for_slice(struct qaic_device *qdev, struct sg_table **sgt_out,
> struct sg_table *sgt_in, u64 size, u64 offset)
> {
> - int total_len, len, nents, offf = 0, offl = 0;
> struct scatterlist *sg, *sgn, *sgf, *sgl;
> + unsigned int len, nents, offf, offl;
> struct sg_table *sgt;
> + size_t total_len;
> int ret, j;
>
> /* find out number of relevant nents needed for this mem */
> @@ -182,6 +183,8 @@ static int clone_range_of_sgt_for_slice(struct qaic_device *qdev, struct sg_tabl
> sgf = NULL;
> sgl = NULL;
> nents = 0;
> + offf = 0;
> + offl = 0;
Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
>
> size = size ? size : PAGE_SIZE;
> for_each_sgtable_dma_sg(sgt_in, sg, j) {
next prev parent reply other threads:[~2025-03-06 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 17:19 [PATCH] accel/qaic: Fix possible data corruption in BOs > 2G Jeff Hugo
2025-03-06 17:51 ` Lizhi Hou [this message]
2025-03-06 18:37 ` Troy Hanson
2025-03-06 18:41 ` Youssef Samir
2025-03-14 16:35 ` Jeff Hugo
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=554638b5-314b-b0cc-5b91-2cc635f78f7d@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=ogabbay@kernel.org \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_thanson@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