diff options
| author | Hou Tao <houtao1@huawei.com> | 2025-01-20 16:29:49 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-17 11:36:31 +0100 |
| commit | 895698621b6fa1dc49e983457a1c99f29ba7f763 (patch) | |
| tree | 0dc214672770aa90c17227101d5e2d50222d90e4 /arch/mips | |
| parent | ad5e2f7992e4a9eb5fdf69d78b24d956c04d2d51 (diff) | |
| download | linux-895698621b6fa1dc49e983457a1c99f29ba7f763.tar.gz linux-895698621b6fa1dc49e983457a1c99f29ba7f763.tar.bz2 linux-895698621b6fa1dc49e983457a1c99f29ba7f763.zip | |
dm-crypt: don't update io->sector after kcryptd_crypt_write_io_submit()
commit 9fdbbdbbc92b1474a87b89f8b964892a63734492 upstream.
The updates of io->sector are the leftovers when dm-crypt allocated
pages for partial write request. However, since commit cf2f1abfbd0db
("dm crypt: don't allocate pages for a partial request"), there is no
partial request anymore.
After the introduction of write request rb-tree, the updates of
io->sectors may interfere the insertion procedure, because ->sectors of
these write requests which have already been added in the rb-tree may be
changed during the insertion of new write request.
Fix it by removing these buggy updates of io->sectors. Considering these
updates only effect the write request rb-tree, the commit which
introduces the write request rb-tree is used as the fix tag.
Fixes: b3c5fd305249 ("dm crypt: sort writes")
Cc: stable@vger.kernel.org
Signed-off-by: Hou Tao <houtao1@huawei.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/mips')
0 files changed, 0 insertions, 0 deletions
