From: Jakub Kicinski <kuba@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Eric Dumazet <edumazet@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH net-next] net: uapi: Provide an UAPI definition of 'struct sockaddr'
Date: Mon, 5 Jan 2026 09:57:13 -0800 [thread overview]
Message-ID: <20260105095713.0b312b26@kernel.org> (raw)
In-Reply-To: <20260105-uapi-sockaddr-v1-1-b7653aba12a5@linutronix.de>
On Mon, 05 Jan 2026 09:25:55 +0100 Thomas Weißschuh wrote:
> Various UAPI headers reference 'struct sockaddr'. Currently the
> definition of this struct is pulled in from the libc header
> sys/socket.h. This is problematic as it introduces a dependency
> on a full userspace toolchain.
>
> Instead expose a custom but compatible definition of 'struct sockaddr'
> in the UAPI headers. It is guarded by the libc compatibility
> infrastructure to avoid potential conflicts.
>
> The compatibility symbol won't be supported by glibc right away,
> but right now __UAPI_DEF_IF_IFNAMSIZ is not supported either,
> so including the libc headers before the UAPI headers is broken anyways.
I did not look too closely but this seems to break build of selftests
in netdev and BPF CI (netdev on AWS Linux, not sure what base BPF uses)
next prev parent reply other threads:[~2026-01-05 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 8:25 [PATCH net-next] net: uapi: Provide an UAPI definition of 'struct sockaddr' Thomas Weißschuh
2026-01-05 13:50 ` Arnd Bergmann
2026-01-20 18:50 ` [klibc] " H. Peter Anvin
2026-01-20 22:31 ` Arnd Bergmann
2026-01-20 23:20 ` H. Peter Anvin
2026-01-30 11:02 ` Thomas Weißschuh
2026-01-05 17:57 ` Jakub Kicinski [this message]
2026-01-06 10:32 ` Thomas Weißschuh
2026-01-06 23:13 ` Jakub Kicinski
2026-01-09 12:56 ` Arnd Bergmann
2026-01-12 11:42 ` Florian Weimer
2026-01-12 11:55 ` Thomas Weißschuh
2026-01-12 13:25 ` Florian Weimer
2026-01-12 13:33 ` Thomas Weißschuh
2026-01-12 13:37 ` Florian Weimer
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=20260105095713.0b312b26@kernel.org \
--to=kuba@kernel.org \
--cc=arnd@arndb.de \
--cc=edumazet@google.com \
--cc=kuniyu@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.weissschuh@linutronix.de \
--cc=willemb@google.com \
/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