From: Will Deacon <will@kernel.org>
To: anshuman.khandual@arm.com, gshan@redhat.com,
catalin.marinas@arm.com, suzuki.poulose@arm.com,
Zeng Heng <zengheng@huaweicloud.com>
Cc: mark.rutland@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
zengheng4@huawei.com, linux-kernel@vger.kernel.org,
wangkefeng.wang@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: io: Reject non-user protection in ioremap_prot()
Date: Fri, 18 Sep 2026 13:28:08 +0100 [thread overview]
Message-ID: <178972997621.2320119.5986862527529026747.b4-ty@kernel.org> (raw)
In-Reply-To: <20260911015859.71164-1-zengheng@huaweicloud.com>
On Fri, 11 Sep 2026 09:58:59 +0800, Zeng Heng wrote:
> Mapping a stack-top page via /dev/mem with PROT_NONE and then
> reading that process's /proc/<pid>/cmdline triggers a spurious WARN
> in ioremap_prot() through generic_access_phys():
>
> WARNING: ./arch/arm64/include/asm/io.h:275 at generic_access_phys
> Call trace:
> generic_access_phys+0x1c8/0x228 (P)
> __access_remote_vm+0x2b4/0x398
> access_remote_vm+0x14/0x30
> get_mm_cmdline+0xf8/0x2a0
> proc_pid_cmdline_read+0x68/0x120
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: io: Reject non-user protection in ioremap_prot()
https://git.kernel.org/arm64/c/bb756b11ad63
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-09-18 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 1:58 [PATCH v2] arm64: io: Reject non-user protection in ioremap_prot() Zeng Heng
2026-09-11 12:25 ` Will Deacon
2026-09-16 12:35 ` Catalin Marinas
2026-09-16 12:41 ` Catalin Marinas
2026-09-18 12:28 ` 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=178972997621.2320119.5986862527529026747.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=wangkefeng.wang@huawei.com \
--cc=zengheng4@huawei.com \
--cc=zengheng@huaweicloud.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