[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e15019f54d26898e4b67b84c331cd52d09427258.camel@kernel.org>
Date: Wed, 27 Mar 2024 15:15:17 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>,
"keescook@...omium.org" <keescook@...omium.org>, "luto@...nel.org"
<luto@...nel.org>, "dave.hansen@...ux.intel.com"
<dave.hansen@...ux.intel.com>, "debug@...osinc.com" <debug@...osinc.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"Liam.Howlett@...cle.com" <Liam.Howlett@...cle.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"mingo@...hat.com" <mingo@...hat.com>, "christophe.leroy@...roup.eu"
<christophe.leroy@...roup.eu>, "tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>, "peterz@...radead.org"
<peterz@...radead.org>, "bp@...en8.de" <bp@...en8.de>, "x86@...nel.org"
<x86@...nel.org>, "broonie@...nel.org" <broonie@...nel.org>
Cc: "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
"linux-s390@...r.kernel.org"
<linux-s390@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-cxl@...r.kernel.org"
<linux-cxl@...r.kernel.org>, "sparclinux@...r.kernel.org"
<sparclinux@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "io-uring@...r.kernel.org"
<io-uring@...r.kernel.org>, "linux-fsdevel@...r.kernel.org"
<linux-fsdevel@...r.kernel.org>, "nvdimm@...ts.linux.dev"
<nvdimm@...ts.linux.dev>, "bpf@...r.kernel.org" <bpf@...r.kernel.org>
Subject: Re: [PATCH v4 02/14] mm: Switch mm->get_unmapped_area() to a flag
On Wed, 2024-03-27 at 02:42 +0000, Edgecombe, Rick P wrote:
> On Tue, 2024-03-26 at 13:57 +0200, Jarkko Sakkinen wrote:
> > In which conditions which path is used during the initialization of
> > mm
> > and why is this the case? It is an open claim in the current form.
>
> There is an arch_pick_mmap_layout() that arch's can have their own
> rules for. There is also a
> generic one. It gets called during exec.
>
> >
> > That would be nice to have documented for the sake of being
> > complete
> > description. I have zero doubts of the claim being untrue.
>
> ...being untrue?
>
I mean I believe the change itself makes sense, it is just not
fully documented in the commit message.
BR, Jarkko
Powered by blists - more mailing lists