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

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 scheduling is possible. kcryptd_crypt_write_convert() is invoked from preemptible cont

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