Date: Tue, 12 May 2015 10:15:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 200138] [PATCH] Fixed sthread-specific array allocation conflict incurred in libthr by some foreign malloc libraries Message-ID: <bug-200138-16-68UBsTtegP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200138-16@https.bugs.freebsd.org/bugzilla/> References: <bug-200138-16@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=200138 --- Comment #7 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to yuri from comment #6) What does prevent the recursion from going infinite ? And your patch still does not make any sense, since assignment to the curthread->specific only happens after the calloc() returned. This sounds like the application bug anyway, because malloc/calloc interposers must handle the system libraries requirements. -- 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-200138-16-68UBsTtegP>