diff options
| author | Konstantin Komarov <almaz.alexandrovich@paragon-software.com> | 2026-10-07 23:59:11 +0200 |
|---|---|---|
| committer | Konstantin Komarov <almaz.alexandrovich@paragon-software.com> | 2026-10-13 15:44:56 +0200 |
| commit | 8100b9f6561f61529795bd271dd743bdeb06a073 (patch) | |
| tree | 0f1a5d7c909074701ccd935939f8c3ee520ccea3 /tools/lib/python | |
| parent | acde4b7276d5434a4aa097d080c6d14e6381c7d2 (diff) | |
| download | linux-next-8100b9f6561f61529795bd271dd743bdeb06a073.tar.gz linux-next-8100b9f6561f61529795bd271dd743bdeb06a073.zip | |
fs/ntfs3: allow a zero cluster count for resident attributes
ntfs_iomap_begin() rejected a zero cluster count from
attr_data_get_block() as corruption. For a resident attribute this is
a normal result: the data lives in the MFT record, so no clusters are
mapped, and the resident case is handled further down and returns
before the cluster count is used.
Move the check below the RESIDENT_LCN and EOF_LCN handling, so it only
applies to the mapped case where a zero count really does indicate a
broken record.
Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions