diff options
author | Eric Biggers <ebiggers@google.com> | 2017-11-07 23:15:27 +0100 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2017-11-10 12:20:26 +0100 |
commit | 1d9ddde12e3c9bab7f3d3484eb9446315e3571ca (patch) | |
tree | b951622c25b368b0224012e2a463aee35c92d7da /drivers/md/dm-verity-target.c | |
parent | crypto: stm32/hash - Fix return issue on update (diff) | |
download | linux-1d9ddde12e3c9bab7f3d3484eb9446315e3571ca.tar.xz linux-1d9ddde12e3c9bab7f3d3484eb9446315e3571ca.zip |
lib/mpi: call cond_resched() from mpi_powm() loop
On a non-preemptible kernel, if KEYCTL_DH_COMPUTE is called with the
largest permitted inputs (16384 bits), the kernel spends 10+ seconds
doing modular exponentiation in mpi_powm() without rescheduling. If all
threads do it, it locks up the system. Moreover, it can cause
rcu_sched-stall warnings.
Notwithstanding the insanity of doing this calculation in kernel mode
rather than in userspace, fix it by calling cond_resched() as each bit
from the exponent is processed. It's still noninterruptible, but at
least it's preemptible now.
Do the cond_resched() once per bit rather than once per MPI limb because
each limb might still easily take 100+ milliseconds on slow CPUs.
Cc: <stable@vger.kernel.org> # v4.12+
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'drivers/md/dm-verity-target.c')
0 files changed, 0 insertions, 0 deletions