t: Renamed LFS_T_CK -> LFS_T_CKDATA, kept implied LFS_T_CKMETA

Browse Source

It still doesn't make sense to check data without checking metadata, but
keeping this named LFS_T_CKDATA should hopefully clarify what it does
differently from LFS_T_CKMETA.

This implication is also now encoded in the bit pattern:

  LFS_T_CKMETA  0x0100  ---- ---1 ---- ----
  LFS_T_CKDATA  0x0300  ---- --11 ---- ----

In theory a clever user could force only the CKDATA bit to be set, and
such a configuration would _probably_ work fine, but it won't be
supported just to cut down on possible configurations to test.

No code changes:

           code          stack
  before: 35228           2680
  after:  35228 (+0.0%)   2680 (+0.0%)

...

This commit is contained in:

Christopher Haster

2024-07-05 16:06:59 -05:00

parent c258420dd0

commit b7165d51e6

3 changed files with 149 additions and 150 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

tests/test_traversal.toml

+143 -143

File diff suppressed because it is too large Load Diff