md/raid5: fix parity corruption on journal failure#230
Open
kpd-daemon[bot] wants to merge 1 commit into
Open
Conversation
Author
|
Upstream branch: c17fb54 |
Author
|
Upstream branch: c17fb54 |
When operating in write-through journal mode, a journal device failure can lead to parity corruption and silent data loss. This occurs because the current implementation continues to update parity even when journal writes fail, violating the write-through consistency guarantee. Signed-off-by: Meir Elisha <meir.elisha@volumez.com>
kpd-daemon
Bot
force-pushed
the
series/992159=>md-6.16
branch
from
5acca53 to
3ec7906
Compare
This file contains hidden or 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
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.
Pull request for series with
subject: md/raid5: fix parity corruption on journal failure
version: 2
url: https://patchwork.kernel.org/project/linux-raid/list/?series=992159