https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289734
--- Comment #20 from Rick Macklem <[email protected]> --- (In reply to Rick Macklem from comment #19) For example, the new code appears to use the socket ptr "so" as a cookie to uniquely identify the socket. But what prevents the socket ptr from being free'd and then the same memory location being malloc()d for a new socket ptr, resulting in the same cookie for a different socket? -- You are receiving this mail because: You are the assignee for the bug.
