diff options
| author | Hou Tao <houtao1@huawei.com> | 2025-01-20 11:29:51 +0300 |
|---|---|---|
| committer | Mikulas Patocka <mpatocka@redhat.com> | 2025-01-22 00:02:12 +0300 |
| commit | 8b8f8037765757861f899ed3a2bfb34525b5c065 (patch) | |
| tree | 7b23d45b92049eb027c19f586f8d284678e48e25 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 996c451d982d1f3f110a4639d822abcd433336e7 (diff) | |
| download | linux-8b8f8037765757861f899ed3a2bfb34525b5c065.tar.xz | |
dm-crypt: track tag_offset in convert_context
dm-crypt uses tag_offset to index the integrity metadata for each crypt
sector. When the initial crypt_convert() returns BLK_STS_DEV_RESOURCE,
dm-crypt will try to continue the crypt/decrypt procedure in a kworker.
However, it resets tag_offset as zero instead of using the tag_offset
related with current sector. It may return unexpected data when using
random IV or return unexpected integrity related error.
Fix the problem by tracking tag_offset in per-IO convert_context.
Therefore, when the crypt/decrypt procedure continues in a kworker, it
could use the next tag_offset saved in convert_context.
Fixes: 8abec36d1274 ("dm crypt: do not wait for backlogged crypto request completion in softirq")
Cc: stable@vger.kernel.org
Signed-off-by: Hou Tao <houtao1@huawei.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions