summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorHou Tao <houtao1@huawei.com>2025-01-20 11:29:49 +0300
committerMikulas Patocka <mpatocka@redhat.com>2025-01-22 00:02:12 +0300
commit9fdbbdbbc92b1474a87b89f8b964892a63734492 (patch)
tree25859d3b04f1539a2164a8a926d62b5ed412a335 /tools/perf/scripts/python/export-to-sqlite.py
parent2f8c28d0d97313edc36d62cbd505019f36111fd5 (diff)
downloadlinux-9fdbbdbbc92b1474a87b89f8b964892a63734492.tar.xz
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 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions