added fat16/32 superblock detection #15
Merged
Conversation
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
cameronbraid
force-pushed
the
fat-superblock
branch
from
8291635 to
cb60f2e
Compare
cameronbraid
force-pushed
the
fat-superblock
branch
from
cb60f2e to
d318b1e
Compare
Member
|
love it ty ty |
ikeycode
approved these changes
Feb 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I implemented fat16/32 support using ext4 as an example, and some hints from the linux kernel inode for detecting bit count
Not sure about how to do fat12 detection.
Ideally I would use rust union, which zerocopy is working on google/zerocopy#1792, however for this I implemented it without a union to avoid making
--cfgchange