Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, liulhong617@163.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, liulhong617 <liulhong617@gmail.com>
Subject: Re: [PATCH] arm64: mm: fix accidental linear mapping of no-map reserved memory
Date: Thu,  6 Aug 2026 18:11:41 +0100	[thread overview]
Message-ID: <178602241325.427442.8605112911020828131.b4-ty@kernel.org> (raw)
In-Reply-To: <20260513010255.3764038-1-liulhong617@163.com>

On Wed, 13 May 2026 09:02:55 +0800, liulhong617@163.com wrote:
> When reserved-memory regions with the "no-map" property are not
> page-aligned, the kernel may accidentally map them into the linear
> mapping, contradicting the no-map semantics.
> 
> The root cause is a mismatch between /proc/iomem's address boundaries
> and the actual page table mapping boundaries:
> 
> [...]

Applied to arm64 (for-next/mm), thanks!

[1/1] arm64: mm: fix accidental linear mapping of no-map reserved memory
      https://git.kernel.org/arm64/c/7ace06a01efa

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      parent reply	other threads:[~2026-08-06 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  1:02 [PATCH] arm64: mm: fix accidental linear mapping of no-map reserved memory liulhong617
2026-07-16 14:01 ` Will Deacon
2026-07-27  1:55   ` Lianghong Liu
2026-08-04 13:41     ` Will Deacon
2026-08-04 14:24   ` Ard Biesheuvel
2026-08-06 13:16     ` Will Deacon
2026-08-06 17:11 ` Will Deacon [this message]

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=178602241325.427442.8605112911020828131.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liulhong617@163.com \
    --cc=liulhong617@gmail.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