Issue 403018: linux: use /proc/self/exe when exec'ing ourselves

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 403018: linux: use /proc/self/exe when exec'ing ourselves (Closed)

Created:
11 years, 1 month ago by Evan Martin

Modified:
9 years, 7 months ago

Reviewers:
Lei Zhang, jam, agl

CC:
chromium-reviews_googlegroups.com

Visibility:
Public.

Description

linux: use /proc/self/exe when exec'ing ourselves We don't want to ever go out to disk when looking for data after startup, since they can be changed by an update. We *should* just be using the zygote, but the zygote is sandboxed-only for now, and fixing that has a lengthy dependency graph. In the interim, /proc/self/exe is the correct executable and exec'ing it should work as long as the subprocess doesn't need any other files from the Chrome directory. BUG=22703 TEST=Start Chrome. Move away the entire Chrome directory; plugins should still work. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=32486

	Unified diffs	Side-by-side diffs	Stats (+17 lines, -10 lines)			Patch
M	chrome/common/child_process_host.cc	View	1 chunk	+10 lines, -6 lines	0 comments	Download
M	chrome/common/chrome_constants.cc	View	1 chunk	+3 lines, -1 line	0 comments	Download
M	chrome/test/chrome_process_util.cc	View	1 chunk	+4 lines, -3 lines	0 comments	Download