|
|
Chromium Code Reviews|
Created:
3 years, 7 months ago by Thiemo Nagel Modified:
3 years, 6 months ago CC:
chromium-reviews, oshima+watch_chromium.org, davemoore+watch_chromium.org Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionUserPolicyManagerFactoryChromeOS: Elaborate comment
BUG=722374
Review-Url: https://codereview.chromium.org/2891933002
Cr-Commit-Position: refs/heads/master@{#478598}
Committed: https://chromium.googlesource.com/chromium/src/+/bf77209685ba07195bf0c0ba84c2e1d1a78f4491
Patch Set 1 #
Total comments: 2
Patch Set 2 : Revert CHECK() #Messages
Total messages: 43 (33 generated)
The CQ bit was checked by tnagel@chromium.org to run a CQ dry run
Patchset #1 (id:1) has been deleted
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== UserPolicyManagerFactoryChromeOS: Prevent unknown account types BUG=722374 ========== to ========== UserPolicyManagerFactoryChromeOS: Prevent unknown account types At the time of login, account time must not be unknown. Adding CHECK() to rule out the possibility of a policy escape. BUG=722374 ==========
Description was changed from ========== UserPolicyManagerFactoryChromeOS: Prevent unknown account types At the time of login, account time must not be unknown. Adding CHECK() to rule out the possibility of a policy escape. BUG=722374 ========== to ========== UserPolicyManagerFactoryChromeOS: Prevent unknown account types At the time of login, account time must not be unknown. Adding CHECK() to rule out the possibility of a policy escape and to clarify the code. BUG=722374 ==========
tnagel@chromium.org changed reviewers: + atwilson@chromium.org, rsorokin@google.com
Roman, Drew, could you please take a look? Thank you, Thiemo
https://codereview.chromium.org/2891933002/diff/20001/chrome/browser/chromeos... File chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc (right): https://codereview.chromium.org/2891933002/diff/20001/chrome/browser/chromeos... chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc:180: CHECK(false); Is CHECK the right thing here, nor AttemptUserExit() or NOTREACHED? I'm somewhat unclear as to what NOTREACHED does in production code. Is there any chance of a reboot loop if you just CHECK here?
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
https://codereview.chromium.org/2891933002/diff/20001/chrome/browser/chromeos... File chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc (right): https://codereview.chromium.org/2891933002/diff/20001/chrome/browser/chromeos... chrome/browser/chromeos/policy/user_policy_manager_factory_chromeos.cc:180: CHECK(false); On 2017/05/18 15:26:03, Andrew T Wilson (Slow) wrote: > Is CHECK the right thing here, nor AttemptUserExit() or NOTREACHED? I guess AttemptUserExit() is just as good, except maybe that CHECK() acts with greater prejudice (I'm slightly put off by the "Attempt" wording) and also conceptually this is something that (supposedly) is prevented by program logic and thus CHECK() would seem like the correct way to express that. > I'm somewhat unclear as to what NOTREACHED does in production code. In production it just logs an error. > Is there any chance of a reboot loop if you just CHECK here? I don't think so because for the login profile we bail above.
rsorokin@google.com changed reviewers: + rsorokin@chromium.org - rsorokin@google.com
lgtm
Drew, friendly ping?
lgtm
The CQ bit was checked by tnagel@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by tnagel@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by tnagel@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by tnagel@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #2 (id:40001) has been deleted
Patchset #2 (id:60001) has been deleted
Patchset #2 (id:80001) has been deleted
Roman, ptal. It turns out that KioskAppManager hasn't been migrated yet. Thus right now, we can't CHECK() on unknown account types.
Description was changed from ========== UserPolicyManagerFactoryChromeOS: Prevent unknown account types At the time of login, account time must not be unknown. Adding CHECK() to rule out the possibility of a policy escape and to clarify the code. BUG=722374 ========== to ========== UserPolicyManagerFactoryChromeOS: Elaborate comment BUG=722374 ==========
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
lgtm
The CQ bit was checked by tnagel@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from atwilson@chromium.org Link to the patchset: https://codereview.chromium.org/2891933002/#ps100001 (title: "Revert CHECK()")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 100001, "attempt_start_ts": 1497272492168860,
"parent_rev": "d59edeefb6bfb8e4abe9c2c2ff313baf5f47b513", "commit_rev":
"bf77209685ba07195bf0c0ba84c2e1d1a78f4491"}
Message was sent while issue was closed.
Description was changed from ========== UserPolicyManagerFactoryChromeOS: Elaborate comment BUG=722374 ========== to ========== UserPolicyManagerFactoryChromeOS: Elaborate comment BUG=722374 Review-Url: https://codereview.chromium.org/2891933002 Cr-Commit-Position: refs/heads/master@{#478598} Committed: https://chromium.googlesource.com/chromium/src/+/bf77209685ba07195bf0c0ba84c2... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:100001) as https://chromium.googlesource.com/chromium/src/+/bf77209685ba07195bf0c0ba84c2... |
