)]}' { "commit": "0bacb337d5f38ec41dbd941ac31001942a13898e", "tree": "ae8f89d8f761e8eb6e3e375bfb6edd24705fc1ce", "parents": [ "8c78090087603efe16ffa651bd72a0bf367111a6" ], "author": { "name": "Peter Shih", "email": "pihsun@chromium.org", "time": "Tue Nov 27 16:14:06 2018 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Nov 29 12:11:20 2018 -0800" }, "message": "update_kernel: Remove multiple cros_secure from remote_bootargs.\n\nupdate_kernel.sh get remote_bootargs from /proc/cmdline, which includes\nthe \u0027cros_secure\u0027 prepended by depthcharge. This cause the cmdline to\ncontain multiple instances of \u0027cros_secure\u0027 after multiple run of\n`update_kernel.sh --remote_bootargs`, and eventually cause kernel to\nrefuse to boot because of too long cmdline.\n\nFix this by removing continuous repeating cros_secure flag from\nremote_bootargs in update_kernel.sh.\n\nBUG\u003dchromium:907772\nTEST\u003dmanually, run `update_kernel.sh --remote_bootargs` multiple times,\n and see that `cat /proc/cmdline` on DUT still have only two\n cros_secure.\n\nChange-Id: I308043648547cbb5ed6006cc436f56068848ab6a\nReviewed-on: https://chromium-review.googlesource.com/1351176\nCommit-Ready: ChromeOS CL Exonerator Bot \u003cchromiumos-cl-exonerator@appspot.gserviceaccount.com\u003e\nTested-by: Pi-Hsun Shih \u003cpihsun@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "9f7e4080e1160f38dcfe3052c0418ddeb32f2522", "old_mode": 33261, "old_path": "update_kernel.sh", "new_id": "da2f604f2590002d4637e1b3ee93504c3057e16a", "new_mode": 33261, "new_path": "update_kernel.sh" } ] }