diff options
author | 2021-01-09 15:17:06 +0000 | |
---|---|---|
committer | 2021-01-12 13:51:17 -0500 | |
commit | 8e14f610159d524cd7aac37982826d3ef75c09e8 (patch) | |
tree | 094b5c8c739481d8314bd78d4575050cf12d5e64 /tools/perf/scripts/python/stackcollapse.py | |
parent | dm integrity: fix flush with external metadata device (diff) | |
download | wireguard-linux-8e14f610159d524cd7aac37982826d3ef75c09e8.tar.xz wireguard-linux-8e14f610159d524cd7aac37982826d3ef75c09e8.zip |
dm crypt: do not call bio_endio() from the dm-crypt tasklet
Sometimes, when dm-crypt executes decryption in a tasklet, we may get
"BUG: KASAN: use-after-free in tasklet_action_common.constprop..."
with a kasan-enabled kernel.
When the decryption fully completes in the tasklet, dm-crypt will call
bio_endio(), which in turn will call clone_endio() from dm.c core code. That
function frees the resources associated with the bio, including per bio private
structures. For dm-crypt it will free the current struct dm_crypt_io, which
contains our tasklet object, causing use-after-free, when the tasklet is being
dequeued by the kernel.
To avoid this, do not call bio_endio() from the current tasklet context, but
delay its execution to the dm-crypt IO workqueue.
Fixes: 39d42fa96ba1 ("dm crypt: add flags to optionally bypass kcryptd workqueues")
Cc: <stable@vger.kernel.org> # v5.9+
Signed-off-by: Ignat Korchagin <ignat@cloudflare.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions