diff options
| author | David Timber <dxdt@dev.snart.me> | 2026-09-05 17:10:42 +0000 |
|---|---|---|
| committer | Namjae Jeon <linkinjeon@kernel.org> | 2026-10-21 08:28:29 +0900 |
| commit | d090f9f99a73786c85176c41a91020068bca008f (patch) | |
| tree | dc9af0c901a39c62a7d63948d14b2cc5b15b13aa /scripts/Makefile.thinlto | |
| parent | 7d390ca06fe71b6959c8c983a9e43230220029e4 (diff) | |
| download | linux-d090f9f99a73786c85176c41a91020068bca008f.tar.gz linux-d090f9f99a73786c85176c41a91020068bca008f.zip | |
exfat: update percent_in_use field when updating volume flags
Currently, the exfat fs implementation does not modify the
percent_in_use in the boot sector header at all. Although the field is
only an advisory field for situations where bit counting is not
feasible, not updating the field at all can cause confusion if the
the value is actually exposed to the user.
Calculate the value using integer arithmetic only when the dirty flag is
cleared. If the dirty flag is set, set to 0xFF.
It is set to 0xFF when mounting under the assumption that the number of
used clusters will change - this is basically what is recommended in the
SD Association's specs.
When clearing the dirty flag, if overridden by
sbi->vol_flags_persistent, set to 0xFF. This is intentional because if
there are orphan clusters, the calculated value would be incorrect and
correcting the fs error is fsck.exfat's job.
Signed-off-by: David Timber <dxdt@dev.snart.me>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
