From: Jason Gunthorpe <jgg@nvidia.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
David Hildenbrand <david@redhat.com>,
akpm@linux-foundation.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: get_user_pages() and EXEC_ONLY mapping.
Date: Fri, 10 Nov 2023 10:53:06 -0400 [thread overview]
Message-ID: <20231110145306.GP4488@nvidia.com> (raw)
In-Reply-To: <87bkc1oe8c.fsf@linux.ibm.com>
On Fri, Nov 10, 2023 at 08:19:23PM +0530, Aneesh Kumar K.V wrote:
>
> Hello,
>
> Some architectures can now support EXEC_ONLY mappings and I am wondering
> what get_user_pages() on those addresses should return.
-EPERM
> Earlier PROT_EXEC implied PROT_READ and pte_access_permitted()
> returned true for that. But arm64 does have this explicit comment
> that says
>
> /*
> * p??_access_permitted() is true for valid user mappings (PTE_USER
> * bit set, subject to the write permission check). For execute-only
> * mappings, like PROT_EXEC with EPAN (both PTE_USER and PTE_UXN bits
> * not set) must return false. PROT_NONE mappings do not have the
> * PTE_VALID bit set.
> */
>
> Is that correct? We should be able to get struct page for PROT_EXEC
> mappings?
If the memory is unreadable then providing a back door through
O_DIRECT and everthing else to read it sounds wrong to me.
If there is some case where a get_user_pages caller is exec-only
compatible then a new FOLL_EXEC flag to permit it would make sense.
Jason
next parent reply other threads:[~2023-11-10 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bkc1oe8c.fsf@linux.ibm.com>
2023-11-10 14:53 ` Jason Gunthorpe [this message]
[not found] ` <9a51f827-6bf4-412b-9feb-37cc41ad3e90@linux.ibm.com>
2023-11-10 15:06 ` Jason Gunthorpe
2023-11-10 17:17 ` Catalin Marinas
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=20231110145306.GP4488@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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