| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 19
|
|
| Author |
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges:
|
Would one of you with the problem be willing to add vsyscall=emulate to your kernel command line, reboot, and see if that fixes the errors?
|
||
|
|
redmaw
Cruncher Joined: Apr 14, 2010 Post Count: 6 Status: Offline Project Badges:
|
Would one of you with the problem be willing to add vsyscall=emulate to your kernel command line, reboot, and see if that fixes the errors? Initial results show that this change is working; thank you BobCat13. Turns I was wrong and I did update the kernel, as double checking the logs would have showed. I did not track down all the change logs but in short vsyscall emulation was completely disabled for a while so make sure your kernel is was built less than 10 days ago or the command line option may not work (https://git.archlinux.org/svntogit/packages.g...47adff718907f9768c489f40). |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So, should we be pushing WCG to re-build these apps to allow more secure operation?
|
||
|
|
redmaw
Cruncher Joined: Apr 14, 2010 Post Count: 6 Status: Offline Project Badges:
|
Based on the information in this thread (https://boinc.berkeley.edu/dev/forum_thread.php?id=11734), which I wish I found earlier, I am going to say yes, they should rebuild the applications. I am not an expert on this topic but I can't think of any reason they need to statically link to a glbic version more than 6 years old.
|
||
|
|
[AF>Libristes]Maeda
Cruncher Joined: Sep 1, 2011 Post Count: 43 Status: Offline Project Badges:
|
As the workaround seems to "enable" vulnerabilities, it is not a solution. Any WCG dev around here to fix their apps ?
|
||
|
|
Tom Moorman
Cruncher Joined: Mar 3, 2007 Post Count: 4 Status: Offline Project Badges:
|
I have applied the change as suggested by BobCat13 and Mapping Cancer Markers is now working without computation errors. However, I found this bit from kernel.org about vsyscall:
============= config X86_VSYSCALL_EMULATION bool "Enable vsyscall emulation" if EXPERT default y depends on X86_64 ---help--- This enables emulation of the legacy vsyscall page. Disabling it is roughly equivalent to booting with vsyscall=none, except that it will also disable the helpful warning if a program tries to use a vsyscall. With this option set to N, offending programs will just segfault, citing addresses of the form 0xffffffffff600?00. This option is required by many programs built before 2013, and care should be used even with newer programs if set to N. Disabling this option saves about 7K of kernel size and possibly 4K of additional runtime pagetable memory. =========== So, yea, I am thinking being able to crunch projects other than microbiome maybe is not worth the risk. |
||
|
|
[AF>Libristes]Maeda
Cruncher Joined: Sep 1, 2011 Post Count: 43 Status: Offline Project Badges:
|
As from glibc, maybe it's a good idea and it's time to upgrade apps as we, the volunteers, will also get benefits from this upgrade (like performance).
----------------------------------------[Edit 1 times, last edit by [AF>Libristes]Maeda at Mar 19, 2018 7:42:54 AM] |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges:
|
We will add updating the linux applications to the schedule. These will likely be phased by research project. Keep an eye on the beta test forum for updates.
Thanks, armstrdj |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank-you, Jonathan.
|
||
|
|
|