linux-kernel - Re: [PATCH v3 1/2] x86/devmem: Remove duplicate range_is

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: <b11e30ac-2b6f-4687-b687-3254511a003a@intel.com>
Date: Thu, 17 Apr 2025 12:30:19 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Dan Williams <dan.j.williams@...el.com>, dave.hansen@...ux.intel.com
Cc: Ingo Molnar <mingo@...nel.org>, Naveen N Rao <naveen@...nel.org>,
 Nikolay Borisov <nik.borisov@...e.com>, linux-kernel@...r.kernel.org,
 linux-coco@...ts.linux.dev
Subject: Re: [PATCH v3 1/2] x86/devmem: Remove duplicate range_is_allowed()
 definition

On 4/17/25 12:12, Dan Williams wrote:
> The only thing preventing a common implementation is that
> phys_mem_access_prot_allowed() expects the range check to exit
> immediately when PAT is disabled [2]. I.e. there is no cache conflict to
> manage in that case. This cleanup was noticed on the path to
> considering changing range_is_allowed() policy to blanket deny /dev/mem
> for private (confidential computing) memory.

Yay, removing duplicated code!

Acked-by: Dave Hansen <dave.hansen@...ux.intel.com>