tree a85f6ae162c7fcfc1286a6034a9bb0c57edd8fdf
parent 4d5a5dcd6f974166c8d0f2657e0079a7f3fc5e01
author Vernon Mauery <vernon.mauery@linux.intel.com> 1545177944 -0800
committer Vernon Mauery <vernon.mauery@linux.intel.com> 1545177944 -0800

phosphor-hostlogger: connect with the correct sockaddr size

Abstract unix sockets start with the nul-charater, but are not nul
terminated. In fact, the nul-character has no meaning in the path.
According to the man page unix(7),

abstract:  an abstract socket address is distinguished (from a pathname
           socket) by the fact that sun_path[0] is a null byte ('\0').
           The socket's address in  this  namespace is  given by the
           additional bytes in sun_path that are covered by the
           specified length of the address structure.  (Null bytes in
           the name have no special significance.)

This means that when calling bind/connect, the size of the sockaddr
structure is not sizeof(sockaddr_un), it is sizeof(sockaddr_un) -
sizeof(sun_path) + (path_len)

Change-Id: I8e46d727c7ffc2fa1799274568c414fbbac306a7
Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>