libipl: Checking write flag before applying guard #42
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
Change: Adding checkWriteFlag, which will read the write flag in guard partition, this to see if the guard partition is not corrupt or not. If the write flag is set to 0x00 checkWriteFlag will return true and need to clear the guard records from the partition. Tested: Setting the write flag as 0x00, seeing that guard records are getting clear. Signed-off-by: Chirag Sharma <[email protected]>
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.
Change:
Adding checkWriteFlag, which will read the write flag
in guard partition, this to see if the guard partition
is not corrupt or not. If the write flag is set to 0x00
checkWriteFlag will return true and need to clear the
guard records from the partition.
Tested:
Setting the write flag as 0x00, seeing that guard records
are getting clear.
Signed-off-by: Chirag Sharma [email protected]