diff options
| author | markus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-12 19:25:10 +0000 |
|---|---|---|
| committer | markus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-12 19:25:10 +0000 |
| commit | 4d93b1f629fda9bd2782d4f7bf8aa12f479cc8f3 (patch) | |
| tree | 1e9a028871ff302fed2527c8f5f4900e704f3d71 /content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.h | |
| parent | 3b4c0dbbe11215694653e7597b88ec5394a1f1df (diff) | |
| download | chromium_src-4d93b1f629fda9bd2782d4f7bf8aa12f479cc8f3.zip chromium_src-4d93b1f629fda9bd2782d4f7bf8aa12f479cc8f3.tar.gz chromium_src-4d93b1f629fda9bd2782d4f7bf8aa12f479cc8f3.tar.bz2 | |
If using the suid sandbox, but not using the seccomp sandbox, there is a
good chance that we will produce a zombie process inside of the new
pid namespace. This happens, because we create a short-lived helper
process when setting up the pid namespace, but the new "init" process
never gets around to reaping this process.
It would have reaped it, if it had received a SIGCHLD signal from any
other process that died. But without the seccomp sandbox, that doesn't
happen very frequently.
This changelist reorders instructions so that we always look for dead
children at least once, when starting the mainloop of the new "init"
process. In doing so, we will always find and reap our dead helper
process.
BUG=109944
TEST=Run Chrome with the suid but without the seccomp sandbox, grep for "defunct" processes in the output of "ps auxw". There shouldn't be any.
Review URL: https://chromiumcodereview.appspot.com/9661001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@126188 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/common/gpu/client/webgraphicscontext3d_command_buffer_impl.h')
0 files changed, 0 insertions, 0 deletions