Date: Wed, 21 Aug 2019 15:15:32 +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-28kk5Sd0vO@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 #7 from Konstantin Belousov <kib@FreeBSD.org> --- (In reply to Greg Lewis from comment #6) First, I am not sure what you mean by 'ther reasons a SIGSEGV could occur in the normal stack region (e.g. a buffer overflow)'. If the region is mapped= rw, then SIGSEGV cannot occur on accesses. Second, does JVM use pthread stacks, or is it managing stacks directly by mmap(MAP_STACK) ? If the later, just remove MAP_STACK from the mmap(2) call and see if it is enough. Third, how the guard pages are created ? Do you use mmap(2) or mprotect(2)= ?=20 If the later, try to call mmap(MAP_ANON) before doing mprotect(2) on it. --=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-28kk5Sd0vO>