On 2015-01-27 13:24, Dimstar / Dominique Leuenberger 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).
Are you aware of or can think of any change in the kernel that would cause this to happen?
This is probably commit fee7e49d (mm: propagate error from stack expansion even for guard page).
Or is the error the stackoverflow sample tries to catch, simply no longer meant to be caught by a sigsegv?
I'm affraid it's either undefined behavior or the implementation is free to kill the process with whatever signal it wants :-/. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org