Date: Mon, 05 Nov 2018 14:52:02 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 232986] Use of ifunc in libc causes segfaults Message-ID: <bug-232986-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232986 Bug ID: 232986 Summary: Use of ifunc in libc causes segfaults Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: shawn.webb@hardenedbsd.org In r339898, kib@ introduced the first use of ifunc in userland, specificall= y in libc. This causes issues with dynamically-linked binaries where RELRO+BIND_= NOW is used. This is an issue in HardenedBSD, where RELRO and BIND_NOW are set = by default. In r340137, emaste@ found one and fixed one issue: the enforcement of RELRO= was being done in the RTLD prior to the resolution of the ifunc. I suspect there may be more to do in the RTLD to complete ifunc support in shared libraries, especially ones as critical as libc. This could be seen as a HardenedBSD-specific issue. However, as FreeBSD re-implements parts of HardenedBSD, FreeBSD will likely run across the same issue. Regardless, we at HardenedBSD will work to find the underlying cause, fix it, and (if applicable) upstream the fix. --=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-232986-227>