Date: Tue, 12 Nov 2019 13:12:04 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 241905] SSP setup is not thread-safe ? Message-ID: <bug-241905-29464-6yQdFFwKCr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241905-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-241905-29464@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=3D241905 --- Comment #6 from Kyle Evans <kevans@freebsd.org> --- (In reply to Konstantin Belousov from comment #5) Huh, today I learned about __constructor__ priority, too. =3D-) It looks like it's really only one __constructor__ creating a thread, and t= hat constructor is using whatever the toolchain default is: https://github.com/qemu/qemu/blob/master/util/rcu.c#L376 I guess this is the same as __guard_setup, https://svnweb.freebsd.org/base/head/lib/libc/secure/stack_protector.c?revi= sion=3D332940&view=3Dmarkup#l47 -> I can bump the priority on qemu's to 200 and that sufficiently works aro= und the problem, but it seems like __guard_setup should be specifically lower t= han the default. --=20 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-241905-29464-6yQdFFwKCr>