Milan Broz 4359973586 Fix dm-verity FEC calculation if stored in the same image with hashes. ...

FEC (Forward Error Correction) data should cover the whole data area,
hashes (Merkle tree) and optionally additional metadata (located after hash area).

Unfortunately, if FEC data is stored in the same file as hash, the calculation
wrongly used the whole file size thus overlaps with FEC area itself.
This produces unusable and too large FEC data.

(There is not a problem if FEC image is a separate image.)

This patch fixes the problem, introducing FEC blocks calculation as:

 -If hash device is in a separate image, metadata covers the whole rest of the image after hash area.
  (Unchanged behaviour.)

 -If hash and FEC device is in the image, metadata ends on the FEC area offset.

This should probably fix several issues reported with FEC wrong calculations.

Fixes: #554

2021-02-14 12:24:18 +01:00

..

rs_decode_char.c

Update Copyright year.

2021-01-25 22:00:25 +01:00

rs_encode_char.c

Update Copyright year.

2021-01-25 22:00:25 +01:00

rs.h

Update Copyright year.

2021-01-25 22:00:25 +01:00

verity_fec.c

Fix dm-verity FEC calculation if stored in the same image with hashes.

2021-02-14 12:24:18 +01:00

verity_hash.c

Fix veritysetup exit code for bad root hash with FEC enabled.

2021-02-14 12:24:18 +01:00

verity.c

Fix dm-verity FEC calculation if stored in the same image with hashes.

2021-02-14 12:24:18 +01:00

verity.h

Fix dm-verity FEC calculation if stored in the same image with hashes.

2021-02-14 12:24:18 +01:00