From: Jeff Xu <jeffxu@chromium.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
jeffxu@chromium.org, akpm@linux-foundation.org,
keescook@chromium.org, jannh@google.com,
torvalds@linux-foundation.org, vbabka@suse.cz,
lorenzo.stoakes@oracle.com, adhemerval.zanella@linaro.org,
oleg@redhat.com, avagin@gmail.com, benjamin@sipsolutions.net,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-mm@kvack.org, jorgelo@chromium.org, sroettger@google.com,
hch@lst.de, ojeda@kernel.org, thomas.weissschuh@linutronix.de,
adobriyan@gmail.com, johannes@sipsolutions.net,
pedro.falcato@gmail.com, hca@linux.ibm.com, willy@infradead.org,
anna-maria@linutronix.de, mark.rutland@arm.com,
linus.walleij@linaro.org, Jason@zx2c4.com, deller@gmx.de,
rdunlap@infradead.org, davem@davemloft.net, peterx@redhat.com,
f.fainelli@gmail.com, gerg@kernel.org,
dave.hansen@linux.intel.com, mingo@kernel.org, ardb@kernel.org,
mhocko@suse.com, 42.hyeyoo@gmail.com, peterz@infradead.org,
ardb@google.com, enh@google.com, rientjes@google.com,
groeck@chromium.org, mpe@ellerman.id.au,
aleksandr.mikhalitsyn@canonical.com, mike.rapoport@gmail.com
Subject: Re: [PATCH v6 2/7] selftests: x86: test_mremap_vdso: skip if vdso is msealed
Date: Mon, 24 Feb 2025 13:24:07 -0800 [thread overview]
Message-ID: <CABi2SkVyOj_nxHnj6RueCoADVbQY1tpz-GbH1Y9pu6qdZ5OMZA@mail.gmail.com> (raw)
In-Reply-To: <6oak6ibdf7yxan3cos3brcqojgjeud4rhlii5nlrlmu7lckalk@zypcm67ac2vk>
On Mon, Feb 24, 2025 at 1:05 PM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
>
> * jeffxu@chromium.org <jeffxu@chromium.org> [250224 12:45]:
> > From: Jeff Xu <jeffxu@chromium.org>
> >
> > Add code to detect if the vdso is memory sealed, skip the test
> > if it is.
>
> It also skips the test if fopen fails on smaps, but maybe that's super
> rare?
>
If we can't access /proc/pid/smaps, that's an "environment" issue
unrelated to this test, therefore skip().
> >
> > Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> > ---
> > .../testing/selftests/x86/test_mremap_vdso.c | 38 +++++++++++++++++++
> > 1 file changed, 38 insertions(+)
> >
> > diff --git a/tools/testing/selftests/x86/test_mremap_vdso.c b/tools/testing/selftests/x86/test_mremap_vdso.c
> > index d53959e03593..c68077c56b22 100644
> > --- a/tools/testing/selftests/x86/test_mremap_vdso.c
> > +++ b/tools/testing/selftests/x86/test_mremap_vdso.c
> > @@ -14,6 +14,7 @@
> > #include <errno.h>
> > #include <unistd.h>
> > #include <string.h>
> > +#include <stdbool.h>
> >
> > #include <sys/mman.h>
> > #include <sys/auxv.h>
> > @@ -55,13 +56,50 @@ static int try_to_remap(void *vdso_addr, unsigned long size)
> >
> > }
> >
> > +#define VDSO_NAME "[vdso]"
> > +#define VMFLAGS "VmFlags:"
> > +#define MSEAL_FLAGS "sl"
> > +#define MAX_LINE_LEN 512
> > +
> > +bool vdso_sealed(FILE *maps)
> > +{
> > + char line[MAX_LINE_LEN];
> > + bool has_vdso = false;
> > +
> > + while (fgets(line, sizeof(line), maps)) {
> > + if (strstr(line, VDSO_NAME))
> > + has_vdso = true;
> > +
> > + if (has_vdso && !strncmp(line, VMFLAGS, strlen(VMFLAGS))) {
> > + if (strstr(line, MSEAL_FLAGS))
> > + return true;
> > +
> > + return false;
> > + }
> > + }
> > +
> > + return false;
> > +}
> > +
> > int main(int argc, char **argv, char **envp)
> > {
> > pid_t child;
> > + FILE *maps;
> >
> > ksft_print_header();
> > ksft_set_plan(1);
> >
> > + maps = fopen("/proc/self/smaps", "r");
> > + if (!maps) {
> > + ksft_test_result_skip("Could not open /proc/self/smaps\n");
>
> fork() below prints errno, should this also print errno?
>
Sure.
> > + return 0;
>
> I guess the logic here is that you might fail later because it's sealed
> but you don't know? Is this rare enough not to matter?
>
yes. We should check the "sl" flag of vdso before continuing, or the
results will be unpredictable.
Android currently includes this selftest. In addition, you or someone
commented that the selftest framework can randomly turn on kernel
config and run selftest, so it is necessary to add this check to skip.
> > + }
> > +
> > + if (vdso_sealed(maps)) {
> > + ksft_test_result_skip("vdso is sealed\n");
> > + return 0;
> > + }
> > +
>
> This file also has an #ifdef __i386__ later, Using it here would
> prevent unnecessary scanning of the maps file. Probably not a big deal?
>
> Do you need to close the maps file?
>
OK, I will add close for good coding practice.
Thanks
-Jeff
next prev parent reply other threads:[~2025-02-24 21:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:45 [PATCH v6 0/7] mseal system mappings jeffxu
2025-02-24 17:45 ` [PATCH v6 1/7] mseal, system mappings: kernel config and header change jeffxu
2025-02-24 18:21 ` Dave Hansen
2025-02-24 18:44 ` Jeff Xu
2025-02-24 18:52 ` Dave Hansen
2025-02-24 18:55 ` Kees Cook
2025-02-24 18:59 ` Jeff Xu
2025-02-24 19:02 ` Dave Hansen
2025-02-24 19:10 ` Liam R. Howlett
2025-02-24 19:22 ` Jeff Xu
2025-02-24 19:32 ` Liam R. Howlett
2025-02-24 19:33 ` Jeff Xu
2025-02-24 19:26 ` Kees Cook
2025-02-24 19:34 ` Jeff Xu
2025-02-24 19:03 ` Liam R. Howlett
2025-02-24 19:07 ` Jeff Xu
2025-02-24 19:18 ` Liam R. Howlett
2025-02-24 19:39 ` Jeff Xu
2025-02-24 20:13 ` Liam R. Howlett
2025-02-24 19:10 ` Jeff Xu
2025-02-24 19:25 ` Kees Cook
2025-02-24 19:42 ` Jeff Xu
2025-02-24 20:12 ` Liam R. Howlett
2025-02-24 21:08 ` Jeff Xu
2025-02-24 17:45 ` [PATCH v6 2/7] selftests: x86: test_mremap_vdso: skip if vdso is msealed jeffxu
2025-02-24 19:02 ` Kees Cook
2025-02-24 21:04 ` Liam R. Howlett
2025-02-24 21:24 ` Jeff Xu [this message]
2025-02-24 17:45 ` [PATCH v6 3/7] mseal, system mappings: enable x86-64 jeffxu
2025-02-24 21:06 ` Liam R. Howlett
2025-02-24 17:45 ` [PATCH v6 4/7] mseal, system mappings: enable arm64 jeffxu
2025-02-24 17:45 ` [PATCH v6 5/7] mseal, system mappings: enable uml architecture jeffxu
2025-02-24 17:45 ` [PATCH v6 6/7] mseal, system mappings: uprobe mapping jeffxu
2025-02-24 17:45 ` [PATCH v6 7/7] mseal, system mappings: update mseal.rst jeffxu
2025-02-24 19:04 ` Kees Cook
2025-02-24 20:26 ` Liam R. Howlett
2025-02-24 21:06 ` Jeff Xu
2025-02-24 21:54 ` Jeff Xu
2025-02-25 6:07 ` Lorenzo Stoakes
2025-02-25 22:31 ` Jeff Xu
2025-02-25 22:36 ` Jeff Xu
2025-02-26 6:08 ` Lorenzo Stoakes
2025-02-26 5:27 ` Lorenzo Stoakes
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=CABi2SkVyOj_nxHnj6RueCoADVbQY1tpz-GbH1Y9pu6qdZ5OMZA@mail.gmail.com \
--to=jeffxu@chromium.org \
--cc=42.hyeyoo@gmail.com \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=adhemerval.zanella@linaro.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=anna-maria@linutronix.de \
--cc=ardb@google.com \
--cc=ardb@kernel.org \
--cc=avagin@gmail.com \
--cc=benjamin@sipsolutions.net \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=enh@google.com \
--cc=f.fainelli@gmail.com \
--cc=gerg@kernel.org \
--cc=groeck@chromium.org \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=johannes@sipsolutions.net \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mark.rutland@arm.com \
--cc=mhocko@suse.com \
--cc=mike.rapoport@gmail.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=ojeda@kernel.org \
--cc=oleg@redhat.com \
--cc=pedro.falcato@gmail.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=sroettger@google.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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