lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176908082966.2054641.12981520784317252855.b4-ty@kernel.org>
Date: Thu, 22 Jan 2026 16:59:42 +0000
From: Will Deacon <will@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>,
	Breno Leitao <leitao@...ian.org>
Cc: kernel-team@...roid.com,
	Will Deacon <will@...nel.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	kernel-team@...a.com,
	clm@...com
Subject: Re: [PATCH] arm64: mm: warn once for ioremap attempts on RAM mappings

On Mon, 22 Dec 2025 07:28:55 -0800, Breno Leitao wrote:
> Replace WARN_ON with WARN_ONCE when detecting attempts to ioremap
> RAM. This prevents log spam when a misbehaving driver repeatedly tries
> to map RAM via ioremap.
> 
> A single warning is more than enough to show the broken code path, and
> extra reports don't add extra information.
> 
> [...]

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

[1/1] arm64: mm: warn once for ioremap attempts on RAM mappings
      https://git.kernel.org/arm64/c/53f45f045cbe

Cheers,
-- 
Will

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ