From: Heinz Mauelshagen <heinzm@redhat.com>
To: heinzm@redhat.com, dm-devel@redhat.com
Cc: snitzer@redhat.com
Subject: [PATCH 0/5] dm raid: fix redundancy check and avoid frozen raid recovery
Date: Wed, 13 Dec 2017 03:02:33 +0100 [thread overview]
Message-ID: <cover.1513125666.git.heinzm@redhat.com> (raw)
Patch 1 fixes validate_raid_redundancy() to check the
current raid set level as stored in the superblock rather than
the constructor requested one. In case of a raid0 to raid10
conversion, the related flaw caused a raid10 check on the
given raid0 raid set leading to a divide error.
Patch 2 hardens raid resync/recover/reshape by
retrieving any current related offsets from the active,
uspended mapping thus avoiding frozen raid recovery
across reloads altogether.
Patch 3 ensures 'a' chars during reshaping.
Patch 4 + 5 add simplification and cleanup without functional change.
This series presumes
https://www.redhat.com/archives/dm-devel/2017-December/msg00012.html
or
linux-dm.git, revision-range fbc7c07ec23c..b84cf26924cf
respectively.
Heinz Mauelshagen (5):
dm raid: validate current raid sets redundancy
dm raid: avoid keeping raid set frozen altogether
dm raid: ensure 'a' chars during reshape
dm raid: simplify rs_get_progress()
dm raid: use rs_is_raid*() / comment
Documentation/device-mapper/dm-raid.txt | 1 +
drivers/md/dm-raid.c | 168 ++++++++++++++++++--------------
2 files changed, 98 insertions(+), 71 deletions(-)
--
2.13.6
next reply other threads:[~2017-12-13 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 2:02 Heinz Mauelshagen [this message]
2017-12-13 2:02 ` [PATCH 1/5] dm raid: validate current raid sets redundancy Heinz Mauelshagen
2017-12-13 2:02 ` [PATCH 2/5] dm raid: avoid keeping raid set frozen altogether Heinz Mauelshagen
2017-12-13 2:02 ` [PATCH 3/5] dm raid: ensure 'a' chars during reshape Heinz Mauelshagen
2017-12-13 2:02 ` [PATCH 4/5] dm raid: simplify rs_get_progress() Heinz Mauelshagen
2017-12-13 2:02 ` [PATCH 5/5] dm raid: use rs_is_raid*() / comment Heinz Mauelshagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1513125666.git.heinzm@redhat.com \
--to=heinzm@redhat.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.