> But previously, there were threads per device, so if one IO thread blocks,
quoted text
> 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

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/