> The problem is a change in the semantics of local domain > socket addresses. Previously, they had a fixed size, and the > path name contained within the address was therefor normally > '\0'-terminated. Now the address is the common socket address > part plus the pathname, where the terminating '\0' is _not_ > part of the address. When the kernel copies out some local > domain part, the user has to supply the terminator, if it wants > to use the path as some ordinary string, e.g. in strlen. > > I haven't made up my mind on how to really fix this, but I > tend to include the terminating '\0' within the address. > > Note that there are even programs within our own > distribution which trigger core dumps due to this change > (at least kdump does).
this change should be reverted or fixed! breaking binary compat like this is really unacceptable. can someone please file a PR about it. we should not have to patch and rebuild apps! .mrg.
