aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/lib/kdoc/kdoc_files.py
diff options
context:
space:
mode:
authorHou Tao <houtao1@huawei.com>2025-01-20 16:29:49 +0800
committerMikulas Patocka <mpatocka@redhat.com>2025-01-21 22:02:12 +0100
commit9fdbbdbbc92b1474a87b89f8b964892a63734492 (patch)
tree25859d3b04f1539a2164a8a926d62b5ed412a335 /scripts/lib/kdoc/kdoc_files.py
parentdm-crypt: use bi_sector in bio when initialize integrity seed (diff)
downloadlinux-rng-9fdbbdbbc92b1474a87b89f8b964892a63734492.tar.xz
linux-rng-9fdbbdbbc92b1474a87b89f8b964892a63734492.zip
dm-crypt: don't update io->sector after kcryptd_crypt_write_io_submit()
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>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions