diff options
| author | oshima <oshima@chromium.org> | 2014-12-16 11:34:23 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2014-12-16 19:34:45 +0000 |
| commit | ddc896504d83fa943ede4732ed2c922c7e494154 (patch) | |
| tree | 3d4288f35bb02af5b35b2c490c56a0efe197b209 /pdf | |
| parent | 83785a165bdc1ee1c2c9809f1207a96b123e560b (diff) | |
| download | chromium_src-ddc896504d83fa943ede4732ed2c922c7e494154.zip chromium_src-ddc896504d83fa943ede4732ed2c922c7e494154.tar.gz chromium_src-ddc896504d83fa943ede4732ed2c922c7e494154.tar.bz2 | |
Revert "Use the libc clone wrapper in sys_clone."
This reverts commit d8a593bceaf0a4b38d06a8c13b948202d205f1b6.
Reason for revert: see crbug.com/442817
> Previously, we directly invoked the syscall, which would not update
> libc's PID cache in the child. Although the libc wrapper function
> updates the PID cache, it unfortunately requires that the child run on a
> different stack, even if CLONE_VM is not specified. We work around this
> by briefly switching stacks in the child, then using longjmp to switch
> back. This gives us a version of clone with fork-like behavior, which is
> what we need for starting processes in new namespaces.
>
> BUG=312380
> Committed: https://crrev.com/d8a593bceaf0a4b38d06a8c13b948202d205f1b6
> Cr-Commit-Position: refs/heads/master@{#308510}
BUG=312380, 442817
TBR=rickyz@chromium.org
Review URL: https://codereview.chromium.org/807213002
Cr-Commit-Position: refs/heads/master@{#308636}
Diffstat (limited to 'pdf')
0 files changed, 0 insertions, 0 deletions