Re: [dm-devel] [PATCH 2/6] dm crypt: Handle DM_CRYPT_NO_*_WORKQUEUE more explicit.

On Sat, Feb 13, 2021 at 11:11 AM Sebastian Andrzej Siewior wrote: > > By looking at the handling of DM_CRYPT_NO_*_WORKQUEUE in > kcryptd_queue_crypt() it appears that READ and WRITE requests might be > handled in the tasklet context as long as interrupts are disabled or it > is handled in hardirq

Re: [dm-devel] [PATCH 4/6] dm crypt: Revisit the atomic argument passed to crypt_convert().

On Sat, Feb 13, 2021 at 11:11 AM Sebastian Andrzej Siewior wrote: > > The atomic argument of crypto_convert() is used to decide if > cond_resched() may be invoked. > > kcryptd_crypt_write_continue() and kcryptd_crypt_read_continue() pass > true here but both are invoked by a worker where schedulin