-
Notifications
You must be signed in to change notification settings - Fork 8.1k
zms: fix init if a faulty bit is detected in the next free location #91579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zms: fix init if a faulty bit is detected in the next free location #91579
Conversation
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
will be updated very soone, removing stale label |
@rghaddab Any update on this one? |
@tpambor I will take care of this next week |
55bc5ac
to
9b8b94e
Compare
For devices that need an erase before a write, ZMS do not verify that the next available location in the open sector is filled with the erase_value. Fix this by adding a check at init. Signed-off-by: Riadh Ghaddab <[email protected]>
9b8b94e
to
417ecd6
Compare
|
@tpambor I just noticed that this is an old commit and I already fixed the sonarqubecloud issue. |
For devices that need an erase before a write, ZMS do not verify that the next available location in the open sector is filled with the erase_value.
Fix this by adding a check at init.