From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Brendan Jackman <brendan.jackman@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Brendan Jackman <jackmanb@google.com>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/secretmem: disable under HIGHMEM
Date: Thu, 16 Jul 2026 12:08:07 +0200 [thread overview]
Message-ID: <5653474e-6692-4353-b5d6-e57b6ab76eaf@kernel.org> (raw)
In-Reply-To: <alef-_LMykiBQ2qP@kernel.org>
On 7/15/26 16:58, Mike Rapoport wrote:
> On Wed, Jul 15, 2026 at 03:49:39PM +0200, David Hildenbrand (Arm) wrote:
>> On 7/15/26 15:44, Mike Rapoport wrote:
>>>
>>> No, I mean what Brendan's patch did:
>>>
>>> config SECRETMEM
>>> default y
>>> bool "Enable memfd_secret() system call" if EXPERT
>>> - depends on ARCH_HAS_SET_DIRECT_MAP
>>> + depends on ARCH_HAS_SET_DIRECT_MAP && !HIGHMEM
>>>
>>> We can change gfp_mask as well for the sake of pedancy
>>
>> Why not change the gfp mask only then?
>
> Citing myself from a few emails back:
>
>>> But still with kmap() and friends not being an NOP the promise "kernel does
>>> not map this memory" does not hold.
So you're saying that kmap() would perform a mapping for a non-highmem page?
static inline void *kmap(struct page *page)
{
void *addr;
might_sleep();
if (!PageHighMem(page))
addr = page_address(page);
else
addr = kmap_high(page);
kmap_flush_tlb((unsigned long)addr);
return addr;
}
I'm missing something important.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-16 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 14:48 [PATCH] mm/secretmem: disable under HIGHMEM Brendan Jackman
2026-07-04 6:42 ` Mike Rapoport
2026-07-05 2:26 ` Andrew Morton
2026-07-05 10:46 ` Brendan Jackman
2026-07-05 11:34 ` Mike Rapoport
2026-07-06 8:42 ` David Hildenbrand (Arm)
2026-07-15 11:22 ` Brendan Jackman
2026-07-15 11:33 ` Mike Rapoport
2026-07-15 12:31 ` David Hildenbrand (Arm)
2026-07-15 13:44 ` Mike Rapoport
2026-07-15 13:49 ` David Hildenbrand (Arm)
2026-07-15 14:58 ` Mike Rapoport
2026-07-16 10:08 ` David Hildenbrand (Arm) [this message]
2026-07-16 10:52 ` Mike Rapoport
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=5653474e-6692-4353-b5d6-e57b6ab76eaf@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brendan.jackman@linux.dev \
--cc=jackmanb@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@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