> But previously, there were threads per device, so if one IO thread blocks, > others stacked mappings can continue > Now I see possibility for deadlock there because we have one io thread now > (assuming that 1 CPU situation Alasdair mentioned). That path calls the crypto worker thread, not the IO worker thread? crypto worker should be fine here, only IO worker would be a problem I think because crypto doesn't really block on nested IO. -Andi -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
