dm table: fixup block integrity profile processing
Not very different from what Martin originally proposed but subtle
changes include:
. only register the integrity profile on first table load; subsequent
loads must have a matching integrity profile
- if profile is already registered, verify new table's profile matches
. resume only verifies that the DM device's integrity profile matches
all the underlying devices' profiles.
- if they don't match the DM device's integrity profile is unregistered
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
1 file changed
