From: Mikhail Zaslonko <zaslonko@linux•ibm.com>
To: bpf@vger•kernel.org
Cc: linux-next@vger•kernel.org,
Alexander Egorenkov <egorenar@linux•ibm.com>,
Christian Brauner <brauner@kernel•org>
Subject: Re: linux-next: samples/bpf build error: no member named 'ns_id' in struct ns_common
Date: Tue, 18 Nov 2025 09:02:19 +0100 [thread overview]
Message-ID: <19cda4f5-a201-4133-9ef6-ee5bf44b0f8a@linux.ibm.com> (raw)
In-Reply-To: <9a8eaa37-698d-41ff-a6f8-287b685d7f78@linux.ibm.com>
On 11/17/2025 10:19 PM, Mikhail Zaslonko wrote:
> 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/
Sorry, wrong link. Here is the related patch-series:
https://lore.kernel.org/all/20251110-work-namespace-nstree-fixes-v1-0-e8a9264e0fb9@kernel.org/
>
> Thanks,
> Mikhail Zaslonko
prev parent reply other threads:[~2025-11-18 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=19cda4f5-a201-4133-9ef6-ee5bf44b0f8a@linux.ibm.com \
--to=zaslonko@linux$(echo .)ibm.com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=brauner@kernel$(echo .)org \
--cc=egorenar@linux$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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