Currently, users of libcutlass need to calloc any
struct sockaddr_in memory that gets passed to the
various calls. If not, then the low-level hash keys
become inconsistent. At least in Linux, there appears
to be some padding at the end of struct sockaddr_in
(member name is sin_zero).
The proper behavior for libcutlass would be for any
call that recieves a struct sockaddr_in to build the
hashkey inside the library to ensure that this stuff
gets handled correctly.