diff options
author | David Oberhollenzer <david.oberhollenzer@sigma-star.at> | 2019-08-23 12:10:16 +0200 |
---|---|---|
committer | David Oberhollenzer <david.oberhollenzer@sigma-star.at> | 2019-08-23 12:10:16 +0200 |
commit | 029a8db2701afb0653c6e789c878bb768ceb87e1 (patch) | |
tree | 86b1c8406d6c7755d19017d98406177660403f54 /tests/mknode_slink.c | |
parent | 7c028e224978e1d5a4f207cc42b9eb58d81897dd (diff) |
Do bounds checking in metadata reader
In all cases where metadata blocks are read, we can roughly (in some
cases even preciesly) say in what range those metadata blocks will be,
so it makes sense to throw an error if an attempt is made to wander
outside this range.
Furthermore, when reading from an uncompressed block, it is more reasonable
to check against the actual block bounds than to padd it with 0 bytes.
Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Diffstat (limited to 'tests/mknode_slink.c')
0 files changed, 0 insertions, 0 deletions