linux/tools/testing/selftests/bpf/uprobe_multi.ld

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);
selftests/bpf: add build ID tests Add a new set of tests validating behavior of capturing stack traces with build ID. We extend uprobe_multi target binary with ability to trigger uprobe (so that we can capture stack traces from it), but also we allow to force build ID data to be either resident or non-resident in memory (see also a comment about quirks of MADV_PAGEOUT). That way we can validate that in non-sleepable context we won't get build ID (as expected), but with sleepable uprobes we will get that build ID regardless of it being physically present in memory. Also, we add a small add-on linker script which reorders .note.gnu.build-id section and puts it after (big) .text section, putting build ID data outside of the very first page of ELF file. This will test all the relaxations we did in build ID parsing logic in kernel thanks to freader abstraction. Reviewed-by: Eduard Zingerman <eddyz87@gmail.com> Signed-off-by: Andrii Nakryiko <andrii@kernel.org> Link: https://lore.kernel.org/r/20240829174232.3133883-11-andrii@kernel.org Signed-off-by: Alexei Starovoitov <ast@kernel.org> 2024-08-29 10:42:32 -07:00			`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);`