[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260130081741.425a92e0@kernel.org>
Date: Fri, 30 Jan 2026 08:17:41 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: Eric Dumazet <edumazet@...gle.com>, Kuniyuki Iwashima
<kuniyu@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Willem de Bruijn
<willemb@...gle.com>, "David S. Miller" <davem@...emloft.net>, Simon Horman
<horms@...nel.org>, Shuah Khan <shuah@...nel.org>, Matthieu Baerts
<matttbe@...nel.org>, Mat Martineau <martineau@...nel.org>, Geliang Tang
<geliang@...nel.org>, Mickaël Salaün
<mic@...ikod.net>, Günther Noack <gnoack@...gle.com>,
Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann
<daniel@...earbox.net>, Jesper Dangaard Brouer <hawk@...nel.org>, John
Fastabend <john.fastabend@...il.com>, Stanislav Fomichev <sdf@...ichev.me>,
Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau
<martin.lau@...ux.dev>, Eduard Zingerman <eddyz87@...il.com>, Song Liu
<song@...nel.org>, Yonghong Song <yonghong.song@...ux.dev>, KP Singh
<kpsingh@...nel.org>, Hao Luo <haoluo@...gle.com>, Jiri Olsa
<jolsa@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-api@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
linux-kselftest@...r.kernel.org, mptcp@...ts.linux.dev,
linux-security-module@...r.kernel.org, bpf@...r.kernel.org,
libc-alpha@...rceware.org, Carlos O'Donell <carlos@...hat.com>, Adhemerval
Zanella <adhemerval.zanella@...aro.org>, Rich Felker <dalias@...c.org>,
klibc@...or.com, Florian Weimer <fweimer@...hat.com>
Subject: Re: [PATCH net-next v2 0/4] net: uapi: Provide an UAPI definition
of 'struct sockaddr'
On Fri, 30 Jan 2026 11:34:15 +0100 Thomas Weißschuh wrote:
> > Are all those selftests / samples getting broken by this patch set?
>
> Yes.
>
> Some of them get broken by the new 'struct sockaddr', but some others are
> already broken just by the new transitive inclusion of libc-compat.h.
> So any header starting to use the compatibility machinery may trigger breakage
> in code including UAPI headers before libc header, even for completely new type
> definitions which themselves would not conflict with libc.
Let's split the uAPI header changes from any selftest changes.
If you're saying the the selftests no longer build after the uAPI
header changes then of course we can't apply the patches.
Powered by blists - more mailing lists