On Tue, 27 Jan 2015 13:24:45 +0100 Dimstar / Dominique Leuenberger <dimstar@opensuse.org> wrote:
Dear Kernel hackers,
We're having an interesting case that needs urgent diagnosis in Factory (as it's a ring-1 package, it blocks anything else from entering, as the staging areas all show the same issue).
The issue: libsigsegv fails the test suite since the kernel has been updated to 3.18.3 (before we had 3.18.1).
The test suite is intentionally 'badly written' and is supposed to cause sigsegv for various cases. The current tests failing are around stack overflows. Up to kernel 3.18.1, those reported SIGSEGV back, but it seems nowadays we get a SIGBUS (which is not in scope of a library called libSIGSEGV to be caught).
Looks like a victim of commit f2f5d44bb48707fa2ea231bc554c9f6ccfb1a883. But I'm not sure if the use of RLIMIT_STACK is correct. Anybody else can help? Petr T -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org