* linux-next: samples/bpf build error: no member named 'ns_id' in struct ns_common
@ 2025-11-17 21:19 Mikhail Zaslonko
2025-11-18 8:02 ` Mikhail Zaslonko
0 siblings, 1 reply; 2+ messages in thread
From: Mikhail Zaslonko @ 2025-11-17 21:19 UTC (permalink / raw)
To: bpf; +Cc: linux-next, Alexander Egorenkov, Christian Brauner
Hi,
I’m observing build errors in samples/bpf on linux-next.
- linux-next snapshot: next-20251117
- Architecture: s390x
- Compiler: clang version 20.1.8
Numerous errors of the following type:
In file included from lathist_kern.c:9:
In file included from /root/linux-next/include/linux/ptrace.h:10:
In file included from /root/linux-next/include/linux/pid_namespace.h:11:
/root/linux-next/include/linux/ns_common.h:25:23: error: no member named 'ns_id' in 'struct ns_common'
25 | VFS_WARN_ON_ONCE(ns->ns_id == 0);
| ~~ ^
Appears to be a mismatch between kernel headers and bpf.
On next-20251111 no errors of this type took place.
I figured out the following patch series is likely the cause:
https://lore.kernel.org/all/20251109-namespace-6-19-fixes-v1-0-ae8a4ad5a3b3@kernel.org/
Thanks,
Mikhail Zaslonko
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-11-18 8:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-11-17 21:19 linux-next: samples/bpf build error: no member named 'ns_id' in struct ns_common Mikhail Zaslonko
2025-11-18 8:02 ` Mikhail Zaslonko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox