From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
bpf@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, adobriyan@gmail.com,
shakeel.butt@linux.dev, hannes@cmpxchg.org, ak@linux.intel.com,
osandov@osandov.com, song@kernel.org
Subject: Re: [PATCH v2 bpf-next 10/10] selftests/bpf: add build ID tests
Date: Thu, 25 Jul 2024 13:01:16 -0700 [thread overview]
Message-ID: <CAEf4BzZ6ze_z-DRKu_6t-zJfAHyfMguRiPUhakHnZgvKy26p1w@mail.gmail.com> (raw)
In-Reply-To: <ZqI_MgOo6Y5mWv0O@krava>
On Thu, Jul 25, 2024 at 5:04 AM Jiri Olsa <olsajiri@gmail.com> wrote:
>
> On Wed, Jul 24, 2024 at 03:52:10PM -0700, Andrii Nakryiko wrote:
>
> SNIP
>
> > +extern char build_id_start[];
> > +extern char build_id_end[];
> > +
> > +int __attribute__((weak)) trigger_uprobe(bool build_id_resident)
> > +{
> > + int page_sz = sysconf(_SC_PAGESIZE);
> > + void *addr;
> > +
> > + /* page-align build ID start */
> > + addr = (void *)((uintptr_t)&build_id_start & ~(page_sz - 1));
> > +
> > + /* to guarantee MADV_PAGEOUT work reliably, we need to ensure that
> > + * memory range is mapped into current process, so we unconditionally
> > + * do MADV_POPULATE_READ, and then MADV_PAGEOUT, if necessary
> > + */
> > + madvise(addr, page_sz, MADV_POPULATE_READ);
> > + if (!build_id_resident)
> > + madvise(addr, page_sz, MADV_PAGEOUT);
>
> could this fail? should we at least print the error,
> might be tricky to display that becase it's called through system() ?
I don't think it should, given the correct addr and page_sz. If it
fails, then some selftest that relies on it will fail.
I can add printf(), though, and it will be printed in logs, I think.
>
> jirka
>
> > +
> > + (void)uprobe();
> > +
> > + return 0;
> > +}
> > +
> > int main(int argc, char **argv)
> > {
> > if (argc != 2)
> > @@ -84,6 +121,10 @@ int main(int argc, char **argv)
> > return bench();
> > if (!strcmp("usdt", argv[1]))
> > return usdt();
> > + if (!strcmp("uprobe-paged-out", argv[1]))
> > + return trigger_uprobe(false /* page-out build ID */);
> > + if (!strcmp("uprobe-paged-in", argv[1]))
> > + return trigger_uprobe(true /* page-in build ID */);
> >
> > error:
> > fprintf(stderr, "usage: %s <bench|usdt>\n", argv[0]);
> > diff --git a/tools/testing/selftests/bpf/uprobe_multi.ld b/tools/testing/selftests/bpf/uprobe_multi.ld
> > new file mode 100644
> > index 000000000000..a2e94828bc8c
> > --- /dev/null
> > +++ b/tools/testing/selftests/bpf/uprobe_multi.ld
> > @@ -0,0 +1,11 @@
> > +SECTIONS
> > +{
> > + . = ALIGN(4096);
> > + .note.gnu.build-id : { *(.note.gnu.build-id) }
> > + . = ALIGN(4096);
> > +}
> > +INSERT AFTER .text;
> > +
> > +build_id_start = ADDR(.note.gnu.build-id);
> > +build_id_end = ADDR(.note.gnu.build-id) + SIZEOF(.note.gnu.build-id);
> > +
> > --
> > 2.43.0
> >
> >
next prev parent reply other threads:[~2024-07-25 20:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 22:52 [PATCH v2 bpf-next 00/10] Harden and extend ELF build ID parsing logic Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 01/10] lib/buildid: add single page-based file reader abstraction Andrii Nakryiko
2024-07-25 12:03 ` Jiri Olsa
2024-07-25 19:58 ` Andrii Nakryiko
2024-07-26 12:31 ` Jiri Olsa
2024-07-25 22:43 ` Andi Kleen
2024-07-27 0:26 ` Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 02/10] lib/buildid: take into account e_phoff when fetching program headers Andrii Nakryiko
2024-07-25 12:03 ` Jiri Olsa
2024-07-25 19:59 ` Andrii Nakryiko
2024-07-25 22:45 ` Andi Kleen
2024-07-27 0:30 ` Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 03/10] lib/buildid: remove single-page limit for PHDR search Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 04/10] lib/buildid: rename build_id_parse() into build_id_parse_nofault() Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 05/10] lib/buildid: implement sleepable build_id_parse() API Andrii Nakryiko
2024-07-25 22:46 ` Andi Kleen
2024-07-27 0:36 ` Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 06/10] lib/buildid: don't limit .note.gnu.build-id to the first page in ELF Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 07/10] lib/buildid: harden build ID parsing logic some more Andrii Nakryiko
2024-07-29 16:15 ` Jann Horn
2024-07-29 16:57 ` Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 08/10] bpf: decouple stack_map_get_build_id_offset() from perf_callchain_entry Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 09/10] bpf: wire up sleepable bpf_get_stack() and bpf_get_task_stack() helpers Andrii Nakryiko
2024-07-24 22:52 ` [PATCH v2 bpf-next 10/10] selftests/bpf: add build ID tests Andrii Nakryiko
2024-07-25 12:04 ` Jiri Olsa
2024-07-25 20:01 ` Andrii Nakryiko [this message]
2024-07-25 12:12 ` Jiri Olsa
2024-07-25 20:03 ` Andrii Nakryiko
2024-07-26 12:27 ` Jiri Olsa
2024-07-27 0:37 ` Andrii Nakryiko
2024-07-28 19:38 ` Jiri Olsa
2024-07-30 20:03 ` Andrii Nakryiko
2024-07-30 20:18 ` Jiri Olsa
2025-09-10 6:09 ` Saket Kumar Bhaskar
2025-09-10 14:18 ` Andrii Nakryiko
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=CAEf4BzZ6ze_z-DRKu_6t-zJfAHyfMguRiPUhakHnZgvKy26p1w@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=adobriyan@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=olsajiri@gmail.com \
--cc=osandov@osandov.com \
--cc=shakeel.butt@linux.dev \
--cc=song@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