This makes a lot of assumptions about how the kernel is named
and where it might be located in the /boot. If it's a separate
partition, it could cause additional problems e.g. with systemd
automount if libbpf is used early enough in the boot process (see:
https://github.com/systemd/systemd/issues/41162).

Fixes #955
---
 src/btf.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/btf.c b/src/btf.c
index 40becc9..28d796f 100644
--- a/src/btf.c
+++ b/src/btf.c
@@ -5494,7 +5494,6 @@ struct btf *btf__load_vmlinux_btf(void)
 	const char *sysfs_btf_path = "/sys/kernel/btf/vmlinux";
 	/* fall back locations, trying to find vmlinux on disk */
 	const char *locations[] = {
-		"/boot/vmlinux-%1$s",
 		"/lib/modules/%1$s/vmlinux-%1$s",
 		"/lib/modules/%1$s/build/vmlinux",
 		"/usr/lib/modules/%1$s/kernel/vmlinux",
-- 
2.53.0