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
| ||
|
Date: Thu, 7 Apr 2022 11:44:16 +0200 From: Christoph Hellwig <hch@....de> To: Anshuman Khandual <anshuman.khandual@....com> Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH 2/2] mm/mmap: Clarify protection_map[] indices On Mon, Apr 04, 2022 at 08:48:40AM +0530, Anshuman Khandual wrote: > protection_map[] maps vm_flags access combinations into page protection > value as defined by the platform via __PXXX and __SXXX macros. The array > indices in protection_map[], represents vm_flags access combinations but > it's not very intuitive to derive. This makes it clear and explicit. Looks good: Reviewed-by: Christoph Hellwig <hch@....de>
Powered by blists - more mailing lists