linux-kernel - Re: [PATCH] resource: fix false warning in __request

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250719163144.7524cfec1fe2041742608f80@linux-foundation.org>
Date: Sat, 19 Jul 2025 16:31:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-cxl@...r.kernel.org
Subject: Re: [PATCH] resource: fix false warning in __request_region()

On Sat, 19 Jul 2025 20:26:04 +0900 Akinobu Mita <akinobu.mita@...il.com> wrote:

> A warning is raised when __request_region() detects a conflict with a
> resource whose resource.desc is IORES_DESC_DEVICE_PRIVATE_MEMORY.
> 
> But this warning is only valid for iomem_resources.
> The hmem device resource uses resource.desc as the numa node id, which can
> cause spurious warnings.
> 
> This change fixes this by restricting the warning to only iomem_resource.
> This also adds a missing new line to the warning message.

What are the circumstance which cause this warning?  Are real world
users hitting this?  If so, should we backport this fix into earlier
kernels?