From: stian@itx.no
Cc: Stian Halseth <stian@itx.no>,
Marek Szyprowski <m.szyprowski@samsung.com>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Leon Romanovsky <leon@kernel.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] sparc: iommu/pci_sun4v: fix page alignment in dma mapping
Date: Tue, 17 Feb 2026 17:21:13 +0100 [thread overview]
Message-ID: <20260217162141.4669-2-stian@itx.no> (raw)
From: Stian Halseth <stian@itx.no>
'phys' may include an offset within the page, while 'base_paddr' is already page-aligned.
This caused incorrect DMA mapping in dma_4u_map_phys and dma_4v_map_phys.
Fix both functions by masking phys with IO_PAGE_MASK or subtracting the page offset.
Fixes: 38c0d0ebf520 ("sparc: Use physical address DMA mapping")
Reported-by: Stian Halseth <stian@itx.no>
Suggested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Stian Halseth <stian@itx.no>
---
arch/sparc/kernel/iommu.c | 2 ++
arch/sparc/kernel/pci_sun4v.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/sparc/kernel/iommu.c b/arch/sparc/kernel/iommu.c
index 46ef88bc9c26..f3755a388ac7 100644
--- a/arch/sparc/kernel/iommu.c
+++ b/arch/sparc/kernel/iommu.c
@@ -312,6 +312,8 @@ static dma_addr_t dma_4u_map_phys(struct device *dev, phys_addr_t phys,
if (direction != DMA_TO_DEVICE)
iopte_protection |= IOPTE_WRITE;
+ phys -= offset_in_page(phys);
+
for (i = 0; i < npages; i++, base++, phys += IO_PAGE_SIZE)
iopte_val(*base) = iopte_protection | phys;
diff --git a/arch/sparc/kernel/pci_sun4v.c b/arch/sparc/kernel/pci_sun4v.c
index 791f0a76665f..2f30eeac4861 100644
--- a/arch/sparc/kernel/pci_sun4v.c
+++ b/arch/sparc/kernel/pci_sun4v.c
@@ -411,7 +411,7 @@ static dma_addr_t dma_4v_map_phys(struct device *dev, phys_addr_t phys,
iommu_batch_start(dev, prot, entry);
for (i = 0; i < npages; i++, phys += IO_PAGE_SIZE) {
- long err = iommu_batch_add(phys, mask);
+ long err = iommu_batch_add(phys & IO_PAGE_MASK, mask);
if (unlikely(err < 0L))
goto iommu_map_fail;
}
--
2.53.0
next reply other threads:[~2026-02-17 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 16:21 stian [this message]
2026-02-17 16:38 ` John Paul Adrian Glaubitz
2026-02-17 16:48 ` Stian Halseth
2026-02-17 17:16 ` John Paul Adrian Glaubitz
2026-02-17 17:25 ` Leon Romanovsky
2026-02-17 17:33 ` Stian Halseth
2026-02-17 17:52 ` Leon Romanovsky
2026-02-17 19:41 ` Stian Halseth
2026-02-17 19:43 ` John Paul Adrian Glaubitz
2026-02-17 17:10 ` [PATCH v2] sparc: Fix " stian
2026-02-18 8:48 ` Leon Romanovsky
2026-02-18 10:28 ` Marek Szyprowski
2026-02-18 11:09 ` Stian Halseth
2026-02-18 11:14 ` Leon Romanovsky
2026-02-18 11:40 ` 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=20260217162141.4669-2-stian@itx.no \
--to=stian@itx.no \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®