Re: [PULL 1/3] qemu-sockets: add abstract UNIX domain socket support

["Daniel P. Berrangé" <berrange@redhat.com>]

On Wed, May 20, 2020 at 04:23:50PM +0200, Markus Armbruster wrote:
> I apologize for chiming in so late...
> 
> Daniel P. Berrangé <berrange@redhat.com> writes:
> 
> > From: xiaoqiang zhao <zxq_yx_007@163.com>
> >
> > unix_listen/connect_saddr now support abstract address types
> >
> > two aditional BOOL switches are introduced:
> > tight: whether to set @addrlen to the minimal string length,
> >        or the maximum sun_path length. default is TRUE
> 
> When and why would anyone pass 'tight': false?

In the abstract namespace the length of the socket is critical
information. ie

   "\0foo" (length == 4,  tight=true)

is a completely different socket from

   "\0foo\0..repeated...\0" (length == sizeof(sun_path), tight=false)

In theory you can have any length in between those extremes,
each being a different socket, but in practice no one is that
insane. Apps either use the full length, or the minimal
length. The "tight" terminology is copied from "socat" which
uses this same option name


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|