On Mon, Jan 30, 2017 at 4:19 PM, Justin Cinkelj <justin.cink...@xlab.si> wrote:
> > > Maybe there is one significant difference between osv_execve() befor/after > Nadav's fixed it, and the code above. > osv_execve() tried to set new thread id in the code executed inside that > new thread. So new thread was (1) initialized, (2) scheduled, (3) started > running and (4) reached the line which set the ID. The caller of > osv_execve() continued after (1), so that was the race. > > The code above should be valid after (1), it only tries to access > app->_thread._id. > > Right (I also realized this in my last reply). -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to osv-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
