(8.3) Fix filter to reject other device types than NVMe #77
Conversation
This file contains 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
Signed-off-by: Damien Thenot <[email protected]>
Nambrok
force-pushed
the
3.2.3-8.3-largeblock-fix
branch
from
d39ed89 to
b6994a7
Compare
Wescoeur
approved these changes
Jan 9, 2025
Wescoeur
pushed a commit
that referenced
this pull request
Jan 29, 2025
Signed-off-by: Damien Thenot <[email protected]>
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.
If the 4KiB blocksize device is not a NVMe, the global_filter for VG activation is incorrect. Meaning the VG could enable on top of the real device and the VDI creation will not work.
This new filter disable everything but the loop devices.