Date: Thu, 09 Oct 2014 10:12:52 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194264] crash in unp_gc -> unp_accessable Message-ID: <bug-194264-8-7mb3ZGVv5V@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194264-8@https.bugs.freebsd.org/bugzilla/> References: <bug-194264-8@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=194264 --- Comment #2 from Andriy Gapon <avg@FreeBSD.org> --- Created attachment 148136 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148136&action=edit log of other thread being in sofree -> unp_dispose So, looks like I missed an elephant in the room. There was a thread that was running soclose -> sofree -> unp_dispose on exactly the same socket that unp_gc_process was processing. The socket is 0xfffff801e7420000 (see the previous attachment). So, this is the race. -- 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-194264-8-7mb3ZGVv5V>