On Thu, Oct 23, 2025 at 12:59:59PM +0200, Paolo Abeni wrote:
> On 10/20/25 11:26 PM, Kees Cook wrote:
> > Add flexible sockaddr structure to support addresses longer than the
> > traditional 14-byte struct sockaddr::sa_data limitation without
> > requiring the full 128-byte sa_data of struct sockaddr_storage. This
> > allows the network APIs to pass around a pointer to an object that
> > isn't lying to the compiler about how big it is, but must be accompanied
> > by its actual size as an additional parameter.
> >
> > It's possible we may way to migrate to including the size with the
> > struct in the future, e.g.:
> >
> > struct sockaddr_unspec {
> > u16 sa_data_len;
> > u16 sa_family;
> > u8 sa_data[] __counted_by(sa_data_len);
> > };
> >
> > Signed-off-by: Kees Cook <[email protected]>
>
> Another side note: please include the 'net-next' subj prefix in next
> submissions, otherwise patchwork could be fouled, and the patches will
> not be picked by our CI - I guess we need all the possible testing done
> here ;)
Okay, I've tweaked my workflow automation to attempt this now. I had a
bit of a catch-22 in that I generated the CC list after "git
format-patch" (and format-patch is what has the --prefix option, so I
couldn't see if netdev@ was in the CC list yet...) Anyway, it should be
part of my automation now...
--
Kees Cook
