On Mon, Mar 06 2023 at 8:49P -0500, Hou Tao <hou...@huaweicloud.com> wrote:
> From: Hou Tao <hout...@huawei.com> > > When neither no_read_workqueue nor no_write_workqueue are enabled, > tasklet_trylock() in crypt_dec_pending() may still return false due to > an uninitialized state, and dm-crypt will do io completion in io_queue > instead of current context unnecessarily. Have you actually experienced this? > Fix it by initializing io->tasklet in crypt_io_init(). Really would rather avoid always calling tasklet_init(). But I can optimize it away with a later patch. Mike -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
