bootable/recovery for tokui #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1906334 Change-Id: I5d7635ec6dc52f9349f7ebaed304f26fd445239f
…113d57 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1906334 Change-Id: I46ab2529c774cd5563b9568a9d6eed52e4ca7676
…113d57 am: 905def0 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1906334 Change-Id: Ic4bf79cb42825823f2a63c452d0d6554c218d450
…113d57 am: 905def0 am: 28f5881 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1906334 Change-Id: I7388963d01512dc55a3619603dbae94d16e6554b
Change-Id: Ia436b3298ebbc4ef96909f3500f48d578f0fad49
We can use this interface to instruct the bootloader to either permanently or only for the next reboot enable MTE for userspace or kernel. Bug: 206895651 Change-Id: I7330e43b7c4f94fc5913a7bc0f667b6eab06e111
Change-Id: I3b78cf48679c8f0e494fc1a6d65e725c33e9bb4a
Original change: https://googleplex-android-review.googlesource.com/c/platform/bootable/recovery/+/16468721 Change-Id: Id4fed70b07045a0d2985680e45072aafadf62a9d
…2f1d2f Original change: https://googleplex-android-review.googlesource.com/c/platform/bootable/recovery/+/16468721 Change-Id: Ia1b1fedc2c302983e40e08e0440b9b57b0f0beeb
Change-Id: I91a3cb1108a9d8c1f4627d94b6d40bf13995fcc0
Change-Id: Icdd571cfd444d16f25af5d42b26656a37ebc73dd
Change-Id: Ie7ed48afcb655abc3284a1deb0d002095015670a
Change-Id: Ie10abbdd7a0f8106bd3620bd9b6c2511422ebe8e
parser.yy uses va_start and should include stdarg.h. Bug: 190084016 Test: m USE_HOST_MUSL=true libedify Change-Id: I2747c1233667717fe0a34050a008370502de184a
So it can be used by device-specific codes. Bug: 184693830 Test: m; atest recovery_unit_test Change-Id: I5885334c1bd04214c9cc295f2337306261a1735c
Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1930535 Change-Id: Ife922e712b4915aa36097f825d863f73e8e0d7dd
… am: 31f842f Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1930535 Change-Id: Id77587d8a06b156dbd37ed73fbf191703eeb7cfc
… am: 31f842f am: 7c608af Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1930535 Change-Id: I6417fd6c122e86dbf9655e5524e73691f8320a81
… am: 31f842f am: 7c608af am: 2c48bd4 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1930535 Change-Id: Ia69ca224d64e0f080f88913cf1ed85ec33c3300c
Change-Id: I59240cd3c2dcf0c26314458936ed0dd8679e9e5c
If the verification fails with the key, 'continue' will be performed and the increment of the index at the end of the loop will be skipped. This CL fixes it. Test: check the log and see correct key indexes. Change-Id: I3d1b2b8b4189f5fedbf8828f5e8e0d0b2e277c6a
Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1933119 Change-Id: I8f163a5e5d7209e2ae4a6e65117de2281206bb25
… am: 6e88cc2 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1933119 Change-Id: I81fb0f956f415014cc6b28f576ee827336277e88
… am: 6e88cc2 am: 2ac9924 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1933119 Change-Id: I8082eb049f167fae0ce556b5035e986a5d6541a5
… am: 6e88cc2 am: 2ac9924 am: 6581dc4 Original change: https://android-review.googlesource.com/c/platform/bootable/recovery/+/1933119 Change-Id: I5a215541059f1adb7e341e94d95db05d2a72038d
Change-Id: I5feb31b872c15125879d8c226f6be0fd3918b969
…05a5 Blank merge reason: commit message contains skip directive Original change: https://googleplex-android-review.googlesource.com/c/platform/bootable/recovery/+/18214611 Change-Id: Ic1dd548b68f8d720c5d2e2ee005523c7f8c2dd8a
Change-Id: I1136ca8130b96dd69a0f1157156b3723408a33f4
…dadcf6 -s ours am skip reason: subject contains skip directive Original change: https://googleplex-android-review.googlesource.com/c/platform/bootable/recovery/+/18214750 Change-Id: Idce57eac87ca61b645b729d8a46a1a8dd1c4f907 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Change-Id: Idc27199725117147d0dbf469658e8701a3a4ba36
Auto-generated-cl: translation import Change-Id: I9bac9d53ad64afd44adb5a4a5d5c21901aa314a7
Auto-generated-cl: translation import Change-Id: Iaa7a2faae24efb0ebf937ba446974f09d36fd513
Change-Id: If34c2e1cfcd8dc78a6a1cd86a1ff9695b8d13151
…84ba5b -s ours am skip reason: subject contains skip directive Original change: https://googleplex-android-review.googlesource.com/c/platform/bootable/recovery/+/18397908 Change-Id: Ib8fa79cb44cb6ac814091e6d4a48f573c39924d3 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Change-Id: I172563a931c54d00d3a9c5c53ef2b10928df7e57
Auto-generated-cl: translation import Change-Id: Ib90d1ccd45b3e2621fe151472941329cceccd64b
Change-Id: I3813c6967f1106ad6fc7d901dfe7f9876a427d73
Change-Id: I40ef34f1533ceab45bb8e3d0bfac14c9db9cfac6
Change-Id: I246494991e0aab640c0382442aff47030b7206e3
Change-Id: Ib9e0b88a74c97bb12e6236496b20cf12fc7820c8
Change-Id: I059868929db3b8cd265e35c493dd6882efddf33e
Change-Id: Id2bbc482a5cf9867cbaf2c555bbc30e44c28874b
Change-Id: I2695a5fadf70098a1412b2c4922c9622c8885b30
Change-Id: I43965f80bf0254ff5550c21309c1373178b539b1
Change-Id: Ifc34fc7f007af0e53ea6a38a43563ffe8d408697
Change-Id: I4af0e47335c834694ee18201e11d09bf0e302477
Change-Id: I7abf94ae4b5bdaede7b2e87ba3528ae6f28483cc
Change-Id: I8cce50134aba1b3ed06ddfe3dec84004d744fdbf
Change-Id: I5ef66d612dbe5a098ac0d1cba81239090cf1b7c3
Change-Id: Ic9dee8b1d51e89aaf0b86a6ac59f8eba7fa8bd4a
markakash
pushed a commit
that referenced
this pull request
Aug 26, 2022
The current flow is 1. factory reset formatted raw disk. 2. next boot tries to convert it to metadata encryption 2.a mount sda27 2.b umount sda27 2.c encrypt_inplace() 2.d fsck on dm-x 2.e mount dm-x The #2 flow is unnecessary, if we know the disk will be encrypted. And, that gives a change of the failure when unmounting the raw disk by starting some file operations on /data. That can cause the entire encryption failure. Bug: 208161227 Signed-off-by: Jaegeuk Kim <jaegeuk@google.com> Change-Id: Iaedfeb74bb6abb667efee6dcadf8d66272466ee0
Change-Id: I8a85db8addeb75a2fd60d809c5ed4edc619ef7ed Signed-off-by: Dmitrii <bankersenator@gmail.com> Signed-off-by: karthik1896 <karthik1896@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.