|
|
Created:
6 years, 2 months ago by Robert Sesek Modified:
6 years, 2 months ago CC:
chromium-reviews, Feng Base URL:
https://chromium.googlesource.com/chromium/src.git@master Project:
chromium Visibility:
Public. |
Description[Android] Do not warm up access to the profile directory in isolated services.
This is motivated by a change in the SELinux policies for isolated services:
https://android-review.googlesource.com/#/c/109577/
Committed: https://crrev.com/cb03e2e2687edcd5f43269d513c62fba5751a926
Cr-Commit-Position: refs/heads/master@{#298855}
Patch Set 1 #
Total comments: 2
Messages
Total messages: 19 (6 generated)
rsesek@chromium.org changed reviewers: + dtrainor@chromium.org
dtrainor: You added this file initially, are you the best reviewer for this CL?
dtrainor: ping
lgtm sorry for the delay!
The CQ bit was checked by rsesek@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/630123003/1
rsesek@chromium.org changed reviewers: + jochen@chromium.org
+jochen for OWNERS stamp
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on tryserver.chromium.linux (http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
lgtm
The CQ bit was checked by rsesek@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/630123003/1
Message was sent while issue was closed.
Committed patchset #1 (id:1) as ff947eff605b5e5b55edd2d390e91b2f4efddef5
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/cb03e2e2687edcd5f43269d513c62fba5751a926 Cr-Commit-Position: refs/heads/master@{#298855}
Message was sent while issue was closed.
klobag@chromium.org changed reviewers: + klobag@chromium.org
Message was sent while issue was closed.
https://codereview.chromium.org/630123003/diff/1/chrome/common/chrome_paths_a... File chrome/common/chrome_paths_android.cc (right): https://codereview.chromium.org/630123003/diff/1/chrome/common/chrome_paths_a... chrome/common/chrome_paths_android.cc:55: if (process_type == switches::kRendererProcess) How about the other child process type? Should we check empty string for process_type to ensure it only returns true for browser process? https://code.google.com/p/chromium/codesearch#chromium/src/chrome/app/chrome_...
Message was sent while issue was closed.
https://codereview.chromium.org/630123003/diff/1/chrome/common/chrome_paths_a... File chrome/common/chrome_paths_android.cc (right): https://codereview.chromium.org/630123003/diff/1/chrome/common/chrome_paths_a... chrome/common/chrome_paths_android.cc:55: if (process_type == switches::kRendererProcess) On 2014/10/17 17:41:14, klobag.chromium wrote: > How about the other child process type? > > Should we check empty string for process_type to ensure it only returns true for > browser process? > > https://code.google.com/p/chromium/codesearch#chromium/src/chrome/app/chrome_... I wanted to keep the change scoped small, since I wasn't sure what other process types Chrome used. Would you prefer to only return true if process_type.empty() to match the CHECK? If so, I'll put together a CL to do that.
Message was sent while issue was closed.
Please make this return true for empty string only. All the child processes are created as isolated services on Android, including renderer, utility and soon GPU. |