From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 268FD2DEA70; Tue, 20 Jan 2026 23:21:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768951264; cv=none; b=He/W7yvjDN1XIdFg7aCFJi1riDdua0FDaj/WQHQFrZ98Hk0vvkIXHewRcvEvV1sNWBk7JLsVYqQZJf0kMB8nNT5b/OYfqc36r6qPKIASIMDKbjLuQ2OE80vTBu4/iASX/W+U21wJ4o0K3uNnZE+HtL9MtT1eosPB+xVt96ZbN/w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768951264; c=relaxed/simple; bh=EOo9r3TrGOlPCzXXLeiaU0t5lefaqILPEHn82lGwLHY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Iy6vrcFLT9wiODoXl51LaPE+LEWChbJbV7b94UVKYj03mquWhSTgWfR/fNKsVyPcEl3v378NPKSF8CGIX52ZmJgocfeol6772squPnaFf+TbSDwYlIG9gyiL6nRK8K1NYJsLXrtHdweqr5T7ljfrkp4OzZnWMMMvW+ApDOCZR6E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=fail (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=Xlz2cAjS reason="signature verification failed"; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="Xlz2cAjS" Received: from [IPV6:2601:646:8081:9483:12c5:bc8e:d949:3497] ([IPv6:2601:646:8081:9483:12c5:bc8e:d949:3497]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 60KNKNir080295 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 20 Jan 2026 15:20:40 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 60KNKNir080295 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2025122301; t=1768951242; bh=TyVCzCgQKQUFRX26Pu8MkQHNVCDWfMBAt0MAhktz1fY=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Xlz2cAjSDtxaY6byoGvYUO33ZXBH7NnXU+2iqWNiJS9IsirvT7SMBT3VGjN8oFcYL 6L2mEsuCj23a69+jkcjgPRGYu3PKRnXVHIaxjakdow/dWFEMd8qyg7ocJKazCcQW+M ceIzGwZpRU6ngPz6KPc5/IAbEtqWaBrXecbbxQlTatSfld9EGWMkBW0AYfz8lHO1xI qs8M/o2UGdDrYA7rRx+t19PoGtsyM+2UMZde1KqwRieO2Qc6oTum4hqO7uUIWIWAMq bFXerA9NJt6bwTWAcfMEEmSdPmxND85HZY+3Ixa8fLqZd4RMgM6HCfC/KCiRbeW+ss yNBVAW8CylWJw== Message-ID: <0f257cd0-27cf-4c11-b79c-724f4e22c4bf@zytor.com> Date: Tue, 20 Jan 2026 15:20:18 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [klibc] [PATCH net-next] net: uapi: Provide an UAPI definition of 'struct sockaddr' To: Arnd Bergmann , =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= , Eric Dumazet , Kuniyuki Iwashima , Paolo Abeni , Willem de Bruijn , Xi Ruoyao , "Carlos O'Donell" , Adhemerval Zanella Netto , Rich Felker Cc: Netdev , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, klibc@zytor.com References: <20260105-uapi-sockaddr-v1-1-b7653aba12a5@linutronix.de> <934ca004-0aef-49a4-a4f1-3d39a2e71864@app.fastmail.com> <0fc5b4ef-c468-416f-a065-f64989d75378@zytor.com> <212d2e51-abc1-47bb-8666-755917cad889@app.fastmail.com> Content-Language: en-US, sv-SE From: "H. Peter Anvin" In-Reply-To: <212d2e51-abc1-47bb-8666-755917cad889@app.fastmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 2026-01-20 14:31, Arnd Bergmann wrote: >> > I must have accidentally cut that from my reply, sorry. > Looking at it again now, I think I ran into problems with the > flexible array that was removed from the in-kernel sockaddr > structure in commit 2b5e9f9b7e41 ("net: Convert struct sockaddr > to fixed-size "sa_data[14]""), so there is a good chance it works > now with the (once more) fixed-size version. > > The other problem is that the structures that embed 'sockaddr' > are used a lot inside of the kernel, in particular in 'ifreq', > so changing the uapi sockaddr to __kernel_sockaddr requires > additional changes wherever the struct members are passed > by reference. > Well, the kernel should do what opting-in libcs do: #define sockaddr __kernel_sockaddr or struct sockaddr { struct __kernel_sockaddr; }; ... now when we have ms extensions turned on. Unfortunately gcc/clang don't support them without the option even with __extension__, so user space is limited to using macros. -hpa