linux-kernel - Re: [PATCH v3 03/12] mm: Use get_unmapped_area

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: <4eb19ee2-e71e-40a7-bc4c-33df5c12d458@csgroup.eu>
Date: Wed, 13 Mar 2024 16:49:39 +0000
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>, "debug@...osinc.com"
	<debug@...osinc.com>, "luto@...nel.org" <luto@...nel.org>, "x86@...nel.org"
	<x86@...nel.org>, "Liam.Howlett@...cle.com" <Liam.Howlett@...cle.com>,
	"broonie@...nel.org" <broonie@...nel.org>, "keescook@...omium.org"
	<keescook@...omium.org>, "dave.hansen@...ux.intel.com"
	<dave.hansen@...ux.intel.com>, "hpa@...or.com" <hpa@...or.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "mingo@...hat.com"
	<mingo@...hat.com>, "kirill.shutemov@...ux.intel.com"
	<kirill.shutemov@...ux.intel.com>, "bp@...en8.de" <bp@...en8.de>,
	"tglx@...utronix.de" <tglx@...utronix.de>, "peterz@...radead.org"
	<peterz@...radead.org>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 03/12] mm: Use get_unmapped_area_vmflags()



Le 13/03/2024 à 15:55, Edgecombe, Rick P a écrit :
> On Wed, 2024-03-13 at 09:05 +0000, Christophe Leroy wrote:
>>
>> What about get_area(), what happens to vm_flags in case that function
>> is
>> used ?
> 
> Shadow stack can only be private and anonymous memory. So this way is
> to avoid unnecessary plumbing. And that plumbing becomes quite
> extensive when you start intersecting with the
> f_ops->get_unmapped_area(), so its pretty fortunate.

Ok,


Reviewed-by: Christophe Leroy <christophe.leroy@...roup.eu>