Repository navigation
lvm2 2.03.43 reviewed - #170
Merged
Merged
Conversation
… are in paths nothing here feeds
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
1 participant
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.
lvm2 released 2.03.43 on 2026-09-30, which left the pin at 2.03.42 without a review row and main's pin gate red. WHATS_NEW and WHATS_NEW_DM (1.02.217) name no security fix. Kryptik builds only device-mapper from LVM2 (libdevmapper for cryptsetup, dmsetup); the device-mapper changes are raid reload suppression, vdostats, and hardening of the config parser against deep nesting, a parser that reads no input a zone supplies. The pin stays; the row records the review.