Comment #30 on issue 22703 by sato...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
FWIW, the symlink is broken if you remove the binary.
% readlink /proc/14831/exe
/tmp/a.out (deleted)
--
You received this message b
Comment #29 on issue 22703 by sato...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Evan, you are right. /proc/self/exe is more magical than a regular symlink.
/proc/self/exe tracks the current
binary location, so you
Comment #28 on issue 22703 by m...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Yeah, /proc/self/exe is a little more magic than a normal symlink. It looks
like a
symlink to userspace, but when you ask the kernel to
Comment #27 on issue 22703 by e...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Now I'm confused. If /proc/self/exe is just a symlink, then the "fix" I
did didn't
work at all, as the point of using /proc/self/exe is
Comment #26 on issue 22703 by sato...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Craig, thank you for the info. I'll comment on the change.
--
You received this message because you are listed in the owner
or CC fiel
Comment #25 on issue 22703 by craig.schlen...@chromium.org: All subprocess
creation needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
satorux: Mike M has a change here to fix the process name:
http://codereview.chromium.org/490028/show
--
You received this mes
Comment #24 on issue 22703 by sato...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Evan,
I just found that a program named "exe" appeared when I ran the "top"
command on my Linux box. I first suspected it could
be s
Comment #23 on issue 22703 by bugdro...@chromium.org: All subprocess
creation needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=34117
--
Updates:
Labels: -Size-Medium -ReleaseBlock-Beta
Comment #20 on issue 22703 by e...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
Dropping release block tag since we've worked around this for beta.
This fix may
Comment #17 on issue 22703 by bugdro...@chromium.org: All subprocess
creation needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=32457
--
Updates:
Status: Started
Owner: e...@chromium.org
Comment #13 on issue 22703 by e...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
(No comment was entered for this change.)
--
You received this message
Comment #12 on issue 22703 by a...@golang.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
We know what the long term answer looks like: switch to the seccomp
sandbox, move the
Zygote outside the sandbox and fork via the zygote.
Comment #11 on issue 22703 by e...@chromium.org: All subprocess creation
needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
agl: I wonder if, rather than a plugin-specific zygote, we could get by
with just
fexecve()'ing /proc/self/exe . That is a more conserv
13 matches
Mail list logo
