libsigsegv tests fail with recent kernels

[wizeman]

When using kernel 3.14.29, the check phase fails with exactly the same errors as was recently reported in their mailing list:

https://lists.gnu.org/archive/html/bug-libsigsegv/2015-01/msg00001.html

The original bug reporter suggested this fix:

https://build.opensuse.org/package/view_file/devel:libraries:c_c++/libsigsegv/libsigsegv-kernel-3.18.2.patch?expand=1

[wizeman]

On the other hand, Linus Torvalds seems to be trying to fix this bug in the kernel, acknowledging it as a regression in the userspace/kernel interface. So I think we should just wait for the kernel patches that fix this issue and apply them.

Relevant thread here: http://lists.opensuse.org/opensuse-factory/2015-01/msg00408.html

[falsifian]

Confirmed, I just ran into this with a 3.18.3 kernel.

[vcunat]

3.18.5 as well.

[ghost]

can also confirm that this is an issue for unstable, both for 3.18.3 and 3.14.29.
working around it temporarily with:
packageOverrides = pkgs: rec {
libsigsegv = pkgs.stdenv.lib.overrideDerivation pkgs.libsigsegv (oldAttrs : {
doCheck = false;
}));
};

[ghost]

Seems fixed in 3.18.6:
"vm: make stack guard page errors return VM_FAULT_SIGSEGV rather than SIGBUS"

[wizeman]

@olavks I think that is not a very good workaround, because even though you're disabling the tests, the library will still be broken.

I think a better workaround is that patch I linked to in the first comment. I've been using it since I posted this bug: the tests passed and I haven't noticed anything broken.

[ghost]

That patch isn't necessary as soon as next stable kernel is out:
https://lkml.org/lkml/2015/2/3/856

seems to be just around the corner:
https://lkml.org/lkml/2015/2/3/861

[wizeman]

@olavks I know, I was just commenting about a workaround (specifically, about the workaround you mentioned) :)

[ghost]

@wizeman disabling the check is worse than patching the check to make it work -- I agree, but would rather have a new kernel ASAP :)

[wizeman]

Kernel 3.18.6 is out with the fix, but AFAICT kernel 3.14.32 (which was released in the same day) is not fixed yet...