diff options
| author | Mikulas Patocka <[email protected]> | 2024-02-19 21:30:10 +0100 |
|---|---|---|
| committer | Mike Snitzer <[email protected]> | 2024-02-20 13:34:31 -0500 |
| commit | 50c70240097ce41fe6bce6478b80478281e4d0f7 (patch) | |
| tree | f44173832624cc6b0e0f28059ccf99dfa871c812 | |
| parent | 9177f3c0dea6143d05cac1bbd28668fd0e216d11 (diff) | |
dm-crypt: don't modify the data when using authenticated encryption
It was said that authenticated encryption could produce invalid tag when
the data that is being encrypted is modified [1]. So, fix this problem by
copying the data into the clone bio first and then encrypt them inside the
clone bio.
This may reduce performance, but it is needed to prevent the user from
corrupting the device by writing data with O_DIRECT and modifying them at
the same time.
[1] https://lore.kernel.org/all/[email protected]/T/
Signed-off-by: Mikulas Patocka <[email protected]>
Cc: [email protected]
Signed-off-by: Mike Snitzer <[email protected]>
| -rw-r--r-- | drivers/md/dm-crypt.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c index f745f8508243..14c5be6eda3b 100644 --- a/drivers/md/dm-crypt.c +++ b/drivers/md/dm-crypt.c @@ -2071,6 +2071,12 @@ static void kcryptd_crypt_write_convert(struct dm_crypt_io *io) io->ctx.bio_out = clone; io->ctx.iter_out = clone->bi_iter; + if (crypt_integrity_aead(cc)) { + bio_copy_data(clone, io->base_bio); + io->ctx.bio_in = clone; + io->ctx.iter_in = clone->bi_iter; + } + sector += bio_sectors(clone); crypt_inc_pending(io); |