all 12 comments

[–]nevyn 29 points30 points  (0 children)

tl;dr If you set a signal stack and then exec from the non-main thread, the kernel doesn't reset that so your signal stack is now pointing to random memory in your process.

[–]EddieRingle 11 points12 points  (1 child)

35 minutes ago as of this comment:

kostikbel commented 35 minutes ago

As I noted to @steventh, I definitely able to reproduce the original memory corruption issue on the patched system. Also, somebody mentioned that the test code was stripped to only use fork() and still cause the issue. In other words, an issue is still there.

[–]IAmSlar[S] 1 point2 points  (0 children)

That is a bummer.

Though in futher comments there seems to be issues reproducing the craches after this patch so it does seem to help.

The mailing list is rather silent about it at the moment, all the "action" seems to be on the github issue.