linux-kernel - Re: [PATCH 3/3] x86/mm: Fix wrong usage of 'MAX_ASID

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: <72cab895a33a10d634b672bbc332989d17316fb5.camel@surriel.com>
Date: Sat, 29 Mar 2025 21:11:05 -0400
From: Rik van Riel <riel@...riel.com>
To: Hou Wenlong <houwenlong.hwl@...group.com>, linux-kernel@...r.kernel.org
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, Andy Lutomirski
 <luto@...nel.org>,  Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner
 <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,  Borislav Petkov	
 <bp@...en8.de>, x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 3/3] x86/mm: Fix wrong usage of 'MAX_ASID_AVAILABLE' in
 global ASID allocation

On Sat, 2025-03-29 at 21:05 +0800, Hou Wenlong wrote:
> 'MAX_ASID_AVAILABLE' represents the maximum valid ASID in the current
> definetion, meaning that the available ASID range is [0,
> MAX_ASID_AVAILABLE]. So the actual count of available ASIDs is
> 'MAX_ASID_AVAIABLE + 1'. However, global ASID allocation use this
> value
> as the size of the bitmap, which results in the maximum ASID number
> being excluded from global ASID allocation. To address this issue,
> redefine the 'MAX_ASID_AVAILABLE' as the count of available ASIDs.
> 
> Signed-off-by: Hou Wenlong <houwenlong.hwl@...group.com>

Reviewed-by: Rik van Riel <riel@...riel.com>

-- 
All Rights Reversed.