Today I learned - getpid() in glibc used to cache the result (pid). This was removed in recent glibc because it was "not reliable". What? How can getpid value change over time???? https://sourceware.org/glibc/wiki/Release/2.25#pid_cache_removal …
I don't see why they care about the new function (vs returns-twice) aspect - if you're sandboxing without calling execve after forking, you're not really sandboxing because you leaked all the parent's data to the child...
-
-
Content/renderer processes are exec'ed, but there's also the CLONE_FS'ed chroot helper. I suppose that could all be redone with callbacks, but the longjmp hack also works. My point was mostly just that, if not for pid/tid caching, we'd just syscall(__NR_clone, ...).
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.