From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Rick Edgecombe" <rick.p.edgecombe@intel.com>,
<Liam.Howlett@oracle.com>, <akpm@linux-foundation.org>,
<bp@alien8.de>, <broonie@kernel.org>,
<christophe.leroy@csgroup.eu>, <dave.hansen@linux.intel.com>,
<debug@rivosinc.com>, <hpa@zytor.com>, <keescook@chromium.org>,
<kirill.shutemov@linux.intel.com>, <luto@kernel.org>,
<mingo@redhat.com>, <peterz@infradead.org>, <tglx@linutronix.de>,
<x86@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-s390@vger.kernel.org>, <sparclinux@vger.kernel.org>,
<linux-sgx@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<linux-cxl@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<io-uring@vger.kernel.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH v4 02/14] mm: Switch mm->get_unmapped_area() to a flag
Date: Tue, 26 Mar 2024 13:57:37 +0200 [thread overview]
Message-ID: <D03NWFQM9XP2.1AWMB9VW98Z98@kernel.org> (raw)
In-Reply-To: <20240326021656.202649-3-rick.p.edgecombe@intel.com>
On Tue Mar 26, 2024 at 4:16 AM EET, Rick Edgecombe wrote:
> The mm_struct contains a function pointer *get_unmapped_area(), which
> is set to either arch_get_unmapped_area() or
> arch_get_unmapped_area_topdown() during the initialization of the mm.
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.
That would be nice to have documented for the sake of being complete
description. I have zero doubts of the claim being untrue.
BR, Jarkko
next prev parent reply other threads:[~2024-03-26 11:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 2:16 [PATCH v4 00/14] Cover a guard gap corner case Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 01/14] proc: Refactor pde_get_unmapped_area as prep Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 02/14] mm: Switch mm->get_unmapped_area() to a flag Rick Edgecombe
2024-03-26 3:32 ` Alexei Starovoitov
2024-03-26 11:57 ` Jarkko Sakkinen [this message]
2024-03-27 2:42 ` Edgecombe, Rick P
2024-03-27 13:15 ` Jarkko Sakkinen
2024-03-28 3:32 ` Edgecombe, Rick P
2024-03-27 6:38 ` Dan Williams
2024-03-28 3:31 ` Edgecombe, Rick P
2024-03-26 2:16 ` [PATCH v4 03/14] mm: Introduce arch_get_unmapped_area_vmflags() Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 04/14] mm: Remove export for get_unmapped_area() Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 05/14] mm: Use get_unmapped_area_vmflags() Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 06/14] thp: Add thp_get_unmapped_area_vmflags() Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 07/14] csky: Use initializer for struct vm_unmapped_area_info Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 08/14] parisc: " Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 09/14] powerpc: " Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 10/14] treewide: " Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 11/14] mm: Take placement mappings gap into account Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 12/14] x86/mm: Implement HAVE_ARCH_UNMAPPED_AREA_VMFLAGS Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 13/14] x86/mm: Care about shadow stack guard gap during placement Rick Edgecombe
2024-03-26 2:16 ` [PATCH v4 14/14] selftests/x86: Add placement guard gap test for shstk Rick Edgecombe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D03NWFQM9XP2.1AWMB9VW98Z98@kernel.org \
--to=jarkko@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=debug@rivosinc.com \
--cc=hpa@zytor.com \
--cc=io-uring@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox