From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Jerome Marchand <jmarchan@redhat.com>, bpf@vger.kernel.org
Cc: Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <martin.lau@linux.dev>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Mykyta Yatsenko <yatsenko@meta.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/bpf: Page out as late a possible in file_reader
Date: Mon, 20 Apr 2026 17:52:11 +0100 [thread overview]
Message-ID: <f02fd939-85f7-414a-8b03-a9ebe56c7660@gmail.com> (raw)
In-Reply-To: <20260420134637.2513867-1-jmarchan@redhat.com>
On 4/20/26 2:46 PM, Jerome Marchand wrote:
> The file_reader/on_open_expect_fault fails consistently on my system.
> It expects a page fault on first dynptr read of some range the exe
> file of the current process because it has paged out that page range
> earlier. However a lot can happen to that range (which depending on
> the actual memory layout could contain text section, data section,
> sections )related to dynamic linking...) between the moment it was
> paged out and the moment the bpf program expected to hit a pagefault
> actually run.
>
> A bit of instrumentation with mincore() shows that pages from that
> range were accessed several times before the program is run. In
> particular the call of file_reader__load() seems to fault all the
> range in.
>
> Move the call to madvise(MADV_PAGEOUT) to just before attaching the
> program to minimize the risk of having those page pulled back in from
> under our feet.
>
> Signed-off-by: Jerome Marchand <jmarchan@redhat.com>
> ---
Thank you for the patch, the change looks good. Does it fail
consistently on 4K page size?
Acked-by: Mykyta Yatsenko <yatsenko@meta.com>
> .../selftests/bpf/prog_tests/file_reader.c | 22 +++++++++----------
> 1 file changed, 10 insertions(+), 12 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/file_reader.c b/tools/testing/selftests/bpf/prog_tests/file_reader.c
> index 5cde32b35da44..48aae7ea0e4bb 100644
> --- a/tools/testing/selftests/bpf/prog_tests/file_reader.c
> +++ b/tools/testing/selftests/bpf/prog_tests/file_reader.c
> @@ -10,6 +10,7 @@
>
> const char *user_ptr = "hello world";
> char file_contents[256000];
> +void *addr;
>
> void *get_executable_base_addr(void)
> {
> @@ -26,8 +27,7 @@ void *get_executable_base_addr(void)
> static int initialize_file_contents(void)
> {
> int fd, page_sz = sysconf(_SC_PAGESIZE);
> - ssize_t n = 0, cur, off;
> - void *addr;
> + ssize_t n = 0, cur;
>
> fd = open("/proc/self/exe", O_RDONLY);
> if (!ASSERT_OK_FD(fd, "Open /proc/self/exe\n"))
> @@ -52,16 +52,6 @@ static int initialize_file_contents(void)
> /* page-align base file address */
> addr = (void *)((unsigned long)addr & ~(page_sz - 1));
>
> - /*
> - * Page out range 0..512K, use 0..256K for positive tests and
> - * 256K..512K for negative tests expecting page faults
> - */
> - for (off = 0; off < sizeof(file_contents) * 2; off += page_sz) {
> - if (!ASSERT_OK(madvise(addr + off, page_sz, MADV_PAGEOUT),
> - "madvise pageout"))
> - return errno;
> - }
> -
> return 0;
> }
>
> @@ -90,6 +80,14 @@ static void run_test(const char *prog_name)
> if (!ASSERT_OK(err, "file_reader__load"))
> goto cleanup;
>
> + /*
> + * Page out range 0..512K, use 0..256K for positive tests and
> + * 256K..512K for negative tests expecting page faults
> + */
> + if (!ASSERT_OK(madvise(addr, sizeof(file_contents) * 2, MADV_PAGEOUT),
> + "madvise pageout"))
> + goto cleanup;
> +
> err = file_reader__attach(skel);
> if (!ASSERT_OK(err, "file_reader__attach"))
> goto cleanup;
next prev parent reply other threads:[~2026-04-20 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 13:46 [PATCH] selftests/bpf: Page out as late a possible in file_reader Jerome Marchand
2026-04-20 16:52 ` Mykyta Yatsenko [this message]
2026-04-21 5:59 ` Jerome Marchand
2026-04-21 10:52 ` Jiri Olsa
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=f02fd939-85f7-414a-8b03-a9ebe56c7660@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jmarchan@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yatsenko@meta.com \
--cc=yonghong.song@linux.dev \
/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