|
|
Created:
6 years, 3 months ago by Vitaly Buka (NO REVIEWS) Modified:
6 years, 3 months ago CC:
chromium-reviews, darin-cc_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Project:
chromium Visibility:
Public. |
DescriptionUse SetAlternateDesktop(false) for service process.
Service process may run as windows service and it fails to create a window station.
BUG=410237
Committed: https://crrev.com/13db9e4e90bf7809af656f04a7d5bda626cdc893
Cr-Commit-Position: refs/heads/master@{#293391}
Patch Set 1 : Wed Sep 3 12:15:49 PDT 2014 #Patch Set 2 : Wed Sep 3 15:03:03 PDT 2014 #Patch Set 3 : Wed Sep 3 17:19:26 PDT 2014 #Patch Set 4 : Wed Sep 3 17:28:49 PDT 2014 #
Total comments: 1
Patch Set 5 : Thu Sep 4 10:58:48 PDT 2014 #
Total comments: 2
Patch Set 6 : Thu Sep 4 11:19:11 PDT 2014 #
Total comments: 2
Patch Set 7 : Thu Sep 4 14:14:43 PDT 2014 #Messages
Total messages: 29 (11 generated)
vitalybuka@chromium.org changed reviewers: + jschuh@chromium.org
lgtm. just verify locally that the service launches properly.
vitalybuka@chromium.org changed reviewers: + jam@chromium.org
+jam for switches
jschuh@chromium.org changed reviewers: + cpu@chromium.org - jschuh@chromium.org
jschuh@chromium.org changed reviewers: + jschuh@chromium.org
Adding cpu@, since I'm out.
not lgtm, see http://www.chromium.org/developers/content-module/. service process is a chrome feature; content shouldn't know about it. This should be changed by SandboxedProcessLauncherDelegate. In ServiceSandboxedProcessLauncherDelegate, set *disable_default_policy=true
On 2014/09/03 22:23:21, jschuh (out thru 20-10-2014) wrote: > Adding cpu@, since I'm out. so if it's not straight forward, I'll walk through with debugger and share my findings
Patchset #1 (id:1) has been deleted
Patchset #1 (id:20001) has been deleted
Patchset #2 (id:60001) has been deleted
Carlos, Please take a look. patch #3 is the same as #1, reviewed by Justin, but with addressed John's comment. I have confused Justin saying that #1 didn't work. I probably was running broken local build. Now it works fine. However I just realized maybe the best option is patch #4? according comment PolicyBase::GetAlternateDesktop(), (use_alternate_desktop_ && !alternate_desktop_handle_) is expected there. https://codereview.chromium.org/534413002/diff/120001/sandbox/win/src/sandbox... File sandbox/win/src/sandbox_policy_base.cc (right): https://codereview.chromium.org/534413002/diff/120001/sandbox/win/src/sandbox... sandbox/win/src/sandbox_policy_base.cc:531: if (use_alternate_desktop_ && alternate_desktop_handle_ && this use-case seems should be supported, check comment on line 216
I don't understand why you need to change sandbox. if your patchset 2 was correct, then as i mentioned above an equivalent way of doing this is setting *disable_default_polic=true in ServiceSandboxedProcessLauncherDelegate
On 2014/09/04 16:10:29, jam wrote: > I don't understand why you need to change sandbox. I don't have. Both #2 and #3 works. #4 is the simplest and consistent with other functions in the code. > > if your patchset 2 was correct, then as i mentioned above an equivalent way of > doing this is setting *disable_default_polic=true in > ServiceSandboxedProcessLauncherDelegate
On 2014/09/04 17:50:27, Vitaly Buka wrote: > On 2014/09/04 16:10:29, jam wrote: > > I don't understand why you need to change sandbox. > > I don't have. Both #2 and #3 works. > #4 is the simplest and consistent with other functions in the code. > > > > > if your patchset 2 was correct, then as i mentioned above an equivalent way of > > doing this is setting *disable_default_polic=true in > > ServiceSandboxedProcessLauncherDelegate #2 is not a good option. Probably I would need to move default polity to service and duplicate code. So I'd recommend to choose between #3 and $4.
On 2014/09/04 17:52:52, Vitaly Buka wrote: > On 2014/09/04 17:50:27, Vitaly Buka wrote: > > On 2014/09/04 16:10:29, jam wrote: > > > I don't understand why you need to change sandbox. > > > > I don't have. Both #2 and #3 works. > > #4 is the simplest and consistent with other functions in the code. > > > > > > > > if your patchset 2 was correct, then as i mentioned above an equivalent way > of > > > doing this is setting *disable_default_polic=true in > > > ServiceSandboxedProcessLauncherDelegate > > #2 is not a good option. Probably I would need to move default polity to service > and duplicate code. > So I'd recommend to choose between #3 and $4. Actually we need merge this into Beta branch. Let's commit #3 to avoid unexpected serious consequences. I'll offer #4 to Justin after he come back.
lgtm https://codereview.chromium.org/534413002/diff/140001/chrome/service/service_... File chrome/service/service_utility_process_host.cc (right): https://codereview.chromium.org/534413002/diff/140001/chrome/service/service_... chrome/service/service_utility_process_host.cc:28: nit: no change needed
https://codereview.chromium.org/534413002/diff/140001/chrome/service/service_... File chrome/service/service_utility_process_host.cc (right): https://codereview.chromium.org/534413002/diff/140001/chrome/service/service_... chrome/service/service_utility_process_host.cc:28: On 2014/09/04 18:06:38, jam wrote: > nit: no change needed Done.
lgtm https://codereview.chromium.org/534413002/diff/160001/chrome/service/service_... File chrome/service/service_utility_process_host.cc (right): https://codereview.chromium.org/534413002/diff/160001/chrome/service/service_... chrome/service/service_utility_process_host.cc:56: // ::CreateWindowStation. .. and it fails to create a window station.
https://codereview.chromium.org/534413002/diff/160001/chrome/service/service_... File chrome/service/service_utility_process_host.cc (right): https://codereview.chromium.org/534413002/diff/160001/chrome/service/service_... chrome/service/service_utility_process_host.cc:56: // ::CreateWindowStation. On 2014/09/04 19:04:23, cpu wrote: > .. and it fails to create a window station. Done.
The CQ bit was checked by vitalybuka@chromium.org
The CQ bit was unchecked by vitalybuka@chromium.org
Patchset #8 (id:200001) has been deleted
The CQ bit was checked by vitalybuka@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/vitalybuka@chromium.org/534413002/180001
Message was sent while issue was closed.
Committed patchset #7 (id:180001) as dbed36a1133f4b0258ab3f3d1fc7d4dba407a373
Message was sent while issue was closed.
Patchset 7 (id:??) landed as https://crrev.com/13db9e4e90bf7809af656f04a7d5bda626cdc893 Cr-Commit-Position: refs/heads/master@{#293391} |