Hi Günther, > Date: 2026-11-16 08:35:57+0100 > From: Günther Noack > > Thank you for the review! > > On Mon, Nov 16, 2026 at 12:55:26AM +0000, Kuniyuki Iwashima wrote: > > On Tue, 03 Nov 2026 21:22:06 +0100, Günther Noack wrote: > > > [...] > > > > > > diff --git a/man/man7/unix.7 b/man/man7/unix.7 > > > index 61f06a74359b..c0e2bdbacdd8 100644 > > > --- a/man/man7/unix.7 > > > +++ b/man/man7/unix.7 > > > @@ -538,13 +538,16 @@ .SS Ancillary messages > > > option must be enabled on the socket. > > > .TP > > > .B SCM_SECURITY > > > -Receive the SELinux security context (the security label) > > > -of the peer socket. > > > -The received ancillary data is a null-terminated string containing > > > -the security context. > > > -The receiver should allocate at least > > > -.B NAME_MAX > > > -bytes in the data portion of the ancillary message for this data. > > > +Receive the security context (the security label) > > > +of the peer socket, > > > +as provided by the active Linux Security Module (LSM). > > > +The received ancillary data is a byte buffer. > > > +.IP > > > +The exact format of the security context buffer > > > +is defined by the active major LSM. > > > +For example, > > > +SELinux returns a SELinux label as a string > > > +(including a terminating null byte). > > > > nit: s/null/NUL/ > > > > otherwise looks good > > > > Reviewed-by: Kuniyuki Iwashima > > The "null byte" is spelled in line with the man-pages(7) conventions > for consistency, where it says: > > The preferred term for the byte is "null byte". Avoid writing > "NUL", since it is too easily confused with "NULL". > > So unless you feel strongly about it, I would prefer to keep it as is. Yup, I prefer null byte, even if just for consistency. NUL byte is something I would find okay, but we'd have to rewrite so much text for it. NUL (without saying byte) is the dangerous thing, as a typo might easily convert it to NULL. Cheers, Alex > > –Günther > --