From: Chris Down <chris@chrisdown.name>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
David Hildenbrand <david@kernel.org>, Kees Cook <kees@kernel.org>,
Jeff Xu <jeffxu@chromium.org>, Andrey Vagin <avagin@gmail.com>,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Shuah Khan <shuah@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
linux-mm@kvack.org, linux-hardening@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 3/3] selftests/mseal_system_mappings: Test vdso unmap and remap
Date: Wed, 28 Oct 2026 00:40:32 +0800 [thread overview]
Message-ID: <auDUAN9xAQRQhnCo@chrisdown.name> (raw)
In-Reply-To: <auC7_5XYr31fimvL@gremlin>
Lorenzo Stoakes (ARM) writes:
>Sorry, in mm we require commit messages. Even for tests :)
Sure thing, I'll add one.
>On Tue, Oct 27, 2026 at 07:43:25PM +0800, Chris Down wrote:
>> Signed-off-by: Chris Down <chris@chrisdown.name>
>> ---
>> .../mseal_system_mappings/sysmap_is_sealed.c | 92 +++++++++++++++++++
>> 1 file changed, 92 insertions(+)
>>
>> diff --git a/tools/testing/selftests/mseal_system_mappings/sysmap_is_sealed.c b/tools/testing/selftests/mseal_system_mappings/sysmap_is_sealed.c
>> index ea75ad537620..83b4fadfbfe7 100644
>> --- a/tools/testing/selftests/mseal_system_mappings/sysmap_is_sealed.c
>> +++ b/tools/testing/selftests/mseal_system_mappings/sysmap_is_sealed.c
>
>Why on earth does 'mseal_system_mappings' have its own directory...??
>
>Ugh I don't know how I let this stuff go on the original series :/
>
>Please, for the love of all that's sacred, move these tests over to
>tools/selftests/mm/. This is an mm feature, for our sins...
>
>You can do the move as a prerequisite patch in the series.
Will do, I'll make the move the first patch.
>(And, again, I really do insist on your change doing some cleanup here as
> well rather than extending this stuff.)
Yep, see my reply to 1/3.
>> @@ -10,6 +10,7 @@
>> #include <unistd.h>
>> #include <string.h>
>> #include <stdbool.h>
>> +#include <sys/mman.h>
>> #include <sys/utsname.h>
>> #include <zlib.h>
>>
>> @@ -232,4 +233,95 @@ TEST_F(basic, check_sealed)
>> EXPECT_EQ(expected, sealed);
>> };
>>
>> +static bool find_vdso(unsigned long *start, unsigned long *end)
>> +{
>> + char line[MAX_LINE_LEN];
>> + bool found = false;
>> + FILE *maps;
>> +
>> + maps = fopen("/proc/self/maps", "r");
>> + if (!maps)
>> + return false;
>> +
>> + while (fgets(line, sizeof(line), maps)) {
>> + if (strstr(line, "[vdso]") &&
>> + sscanf(line, "%lx-%lx", start, end) == 2) {
>> + found = true;
>> + break;
>> + }
>> + }
>> +
>> + fclose(maps);
>> + return found;
>> +}
>
>There's shared code for this kind of thing, please don't duplicate a
>/proc/self/maps thing if unnecessary. Also there's a nicer ioctl interface for
>all this.
>
>See vm_utils.[ch].
Oh thank you! I will use that.
>I mean arguably this is an mremap test that belongs with mremap? I guess
>debatable...
Hmm, I'd lean towards keeping it with the sysmap test, since it's really
testing that the seal is enforced on these mappings rather than anything about
mremap() itself, but I don't feel strongly if you insist, just let me know.
>This all just seems like work that should have been done in the past when this
>feature was proposed, and doesn't depend on your changes at all AFAICT? Maybe I
>missed it though.
>
>Valuable in itself, but probably worth sending separately as a result? Otherwise
>it's a little disconnected from the actual change you're making.
Yeah, it doesn't depend on it. I can send it separately on top of the move if
you like, I just don't like touching things without tests where possible.
Thanks for the review!
next prev parent reply other threads:[~2026-10-27 16:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 11:42 [PATCH 0/3] mseal sysmap: Choose system mapping sealing at boot Chris Down
2026-10-27 11:43 ` [PATCH 1/3] mseal sysmap: Add mseal_system_mappings= boot parameter Chris Down
2026-10-27 14:53 ` Lorenzo Stoakes (ARM)
2026-10-27 16:37 ` Chris Down
2026-10-27 16:57 ` Lorenzo Stoakes (ARM)
2026-10-28 4:30 ` Jeff Xu
2026-10-28 5:52 ` Chris Down
2026-10-28 5:55 ` Chris Down
2026-10-28 6:16 ` Jeff Xu
2026-10-28 9:49 ` Lorenzo Stoakes (ARM)
2026-10-28 12:18 ` Pedro Falcato
2026-10-27 11:43 ` [PATCH 2/3] mseal sysmap: Allow with CHECKPOINT_RESTORE, default off Chris Down
2026-10-27 14:57 ` Lorenzo Stoakes (ARM)
2026-10-27 16:37 ` Chris Down
2026-10-27 16:59 ` Lorenzo Stoakes (ARM)
2026-10-27 11:43 ` [PATCH 3/3] selftests/mseal_system_mappings: Test vdso unmap and remap Chris Down
2026-10-27 15:03 ` Lorenzo Stoakes (ARM)
2026-10-27 16:40 ` Chris Down [this message]
2026-10-27 17:02 ` Lorenzo Stoakes (ARM)
2026-10-28 11:43 ` sashiko-bot
2026-10-28 15:34 ` [PATCH 0/3] mseal sysmap: Choose system mapping sealing at boot Andrei Vagin
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=auDUAN9xAQRQhnCo@chrisdown.name \
--to=chris@chrisdown.name \
--cc=akpm@linux-foundation.org \
--cc=alexander@mihalicyn.com \
--cc=avagin@gmail.com \
--cc=corbet@lwn.net \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jmorris@namei.org \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=paul@paul-moore.com \
--cc=pfalcato@suse.de \
--cc=serge@hallyn.com \
--cc=shuah@kernel.org \
--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