From: Leon Romanovsky <leon@kernel.org>
To: Pranjal Shrivastava <praan@google.com>
Cc: iommu@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
Lu Baolu <baolu.lu@linux.intel.com>,
Logan Gunthorpe <logang@deltatee.com>,
Will Deacon <will@kernel.org>,
Shivaji Kant <shivajikant@google.com>,
Jacob Moroni <jmoroni@google.com>
Subject: Re: [PATCH] dma-direct: Fix missing sg_dma_len assignment in P2PDMA bus mappings
Date: Wed, 26 Nov 2025 19:14:56 +0200 [thread overview]
Message-ID: <20251126171456.GH12483@unreal> (raw)
In-Reply-To: <20251126114112.3694469-1-praan@google.com>
On Wed, Nov 26, 2025 at 11:41:12AM +0000, Pranjal Shrivastava wrote:
> Prior to commit a25e7962db0d7 ("PCI/P2PDMA: Refactor the p2pdma mapping
> helpers"), P2P segments were mapped using the pci_p2pdma_map_segment()
> helper. This helper was responsible for populating sg->dma_address,
> marking the bus address, and also setting sg_dma_len(sg).
>
> The refactor[1] removed this helper and moved the mapping logic directly
> into the callers. While iommu_dma_map_sg() was correctly updated to set
> the length in the new flow, it was missed in dma_direct_map_sg().
>
> Thus, in dma_direct_map_sg(), the PCI_P2PDMA_MAP_BUS_ADDR case sets the
> dma_address and marks the segment, but immediately executes 'continue',
> which causes the loop to skip the standard assignment logic at the end:
>
> sg_dma_len(sg) = sg->length;
>
> As a result, when CONFIG_NEED_SG_DMA_LENGTH is enabled, the dma_length
> field remains uninitialized (zero) for P2P bus address mappings. This
> breaks upper-layer drivers (for e.g. RDMA/IB) that rely on sg_dma_len()
> to determine the transfer size.
>
> Fix this by explicitly setting the DMA length in the
> PCI_P2PDMA_MAP_BUS_ADDR case before continuing to the next scatterlist
> entry.
>
> Fixes: a25e7962db0d7 ("PCI/P2PDMA: Refactor the p2pdma mapping helpers")
> Reported-by: Jacob Moroni <jmoroni@google.com>
> Signed-off-by: Pranjal Shrivastava <praan@google.com>
>
> [1]
> https://lore.kernel.org/all/ac14a0e94355bf898de65d023ccf8a2ad22a3ece.1746424934.git.leon@kernel.org/
> ---
> kernel/dma/direct.c | 1 +
> 1 file changed, 1 insertion(+)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2025-11-26 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251126114122eucas1p19e53eb68f957af3fbc87156f7ad73eff@eucas1p1.samsung.com>
2025-11-26 11:41 ` [PATCH] dma-direct: Fix missing sg_dma_len assignment in P2PDMA bus mappings Pranjal Shrivastava
2025-11-26 17:09 ` Logan Gunthorpe
2025-11-26 17:14 ` Leon Romanovsky [this message]
2025-11-26 18:56 ` Shivaji Kant
2025-11-26 21:51 ` Marek Szyprowski
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=20251126171456.GH12483@unreal \
--to=leon@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jmoroni@google.com \
--cc=logang@deltatee.com \
--cc=m.szyprowski@samsung.com \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=shivajikant@google.com \
--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