vsyscall attempted with vsyscall=none: setiathome v8.04 crashes with a SIGSEGV on Linux

Message boards : SETI@home Enhanced : vsyscall attempted with vsyscall=none: setiathome v8.04 crashes with a SIGSEGV on Linux
Message board moderation

To post messages, you must log in.

AuthorMessage
Alien Seeker
Volunteer tester
Avatar

Send message
Joined: 31 Aug 19
Posts: 1
Credit: 1,356
RAC: 0
France
Message 63401 - Posted: 13 Mar 2020, 18:12:14 UTC

I suppose it doesn't matter much with SETI@home ending at the end of the month, I'm mostly posting for reference.

Setiathome v8.04 (stock app) crashes on a Debian stable box with "SIGSEGV: segmentation violation". See the task in question.

The error actually comes from vsyscall being forbidden in recent Linux kernels for security reasons. Indeed, the kernel message is more explicit:
setiathome_8.04[10957] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7ffcbd24f948 ax:ffffffffff600000 si:0 di:7ffcbd24f960


It's a known problem which can be mitigated if the cruncher reboots with the vsyscall=emulate kernel option, but it lowers the computer's security (a bit). The actual long-term solution would be on the project side, to rebuild the app against a newer libc.
Gazing at the skies, hoping for contact... Unlikely, but it would be such a fantastic opportunity to learn.

My alternative profile
ID: 63401 · Report as offensive

Message boards : SETI@home Enhanced : vsyscall attempted with vsyscall=none: setiathome v8.04 crashes with a SIGSEGV on Linux


 
©2021 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.