Date: Tue, 28 Oct 2025 22:06:32 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 289734] panic tcp_usr_close while running mount command after configure NFS over TLS Message-ID: <bug-289734-7501-tDyxpOvqXB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-289734-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-289734-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289734 --- Comment #20 from Rick Macklem <rmacklem@FreeBSD.org> --- (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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-289734-7501-tDyxpOvqXB>