From: "Arnd Bergmann" <arnd@arndb.de>
To: "Karl Mehltretter" <kmehltretter@gmail.com>,
"Russell King" <linux@armlinux.org.uk>
Cc: "Nicolas Pitre" <npitre@baylibre.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Robin Murphy" <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dma-mapping: split cache maintenance at highmem boundary
Date: Wed, 09 Sep 2026 09:24:23 +0200 [thread overview]
Message-ID: <ff220a24-edae-4b75-9873-1a58f5948a01@app.fastmail.com> (raw)
In-Reply-To: <20260909064443.90544-1-kmehltretter@gmail.com>
On Wed, Sep 9, 2026, at 08:44, Karl Mehltretter wrote:
> dma_cache_maint_page() processes highmem pages one at a time, but passes
> the complete remaining range to a cache operation when the current page
> is lowmem. If a physically contiguous range starts in lowmem and crosses
> into highmem, the operation continues beyond high_memory through virtual
> addresses which do not map the highmem pages.
>
> On a Raspberry Pi 400 running an ARM32 LPAE kernel, an 8 KiB scatterlist
> entry crossing this boundary caused a deterministic data abort at f0000000
> in v7_dma_clean_range().
>
> Limit the crossing lowmem iteration to the end of its page. Subsequent
> iterations advance page by page until the existing highmem path takes
> over. Keep the bulk operation for ranges contained in lowmem.
>
> Fixes: 43377453af83 ("[ARM] introduce dma_cache_maint_page()")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
Hi Karl,
I can see how the fix addresses the problem, but I don't yet see
how you can arrive in this situation. What type of memory allocation
can produce a physically contiguous page range from multiple
zones?
Arnd
next prev parent reply other threads:[~2026-09-09 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 6:44 Karl Mehltretter
2026-09-09 7:24 ` Arnd Bergmann [this message]
2026-09-10 6:24 ` Karl Mehltretter
2026-09-10 12:53 ` Robin Murphy
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=ff220a24-edae-4b75-9873-1a58f5948a01@app.fastmail.com \
--to=arnd@arndb.de \
--cc=iommu@lists.linux.dev \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=npitre@baylibre.com \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®