LInux fork/clone can be interrupted by a signal which causes the syscall to restart. The can go on forever with periodic signals. Beware
No, because a signal handler could run after fork in the child, but before they're set correctly.
-
-
If you refrain from using SYS_fork, instead use SYS_clone w/CLONE_CHILD_SETTID, then lazy robustlist init may suffice
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In any case SYS_fork takes about 200-500x the time of SYS_rt_sigprocmask.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.