Date: Tue, 20 Aug 2019 17:48:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239894] security.bsd.stack_guard_page default causes Java to crash Message-ID: <bug-239894-227-GlGKKj2LZv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-239894-227@https.bugs.freebsd.org/bugzilla/> References: <bug-239894-227@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=3D239894 --- Comment #4 from Kurt Miller <kurt@intricatesoftware.com> --- Yes, that's the root of the problem. The JVM needs to be able to deterministically manage its own guard pages independently from both the ke= rnel placed ones and the pthread placed ones. Where 'manage' means change the protection of the pages to PROT_NONE and back to PROT_READ|PROT_WRITE. I think if the issues mentioned in comment #1 that kernel placed guard pages cause pthreads are corrected, it is very likely the JVM will be able to use= the same method as libthr to place its guard pages (currently with mprotect(2)). --=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-239894-227-GlGKKj2LZv>