From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lib/mpi: call cond_resched() from mpi_powm() loop
Date: Mon, 27 Nov 2017 13:13:05 +0100 [thread overview]
Message-ID: <20171127121305.GB28339@kroah.com> (raw)
In-Reply-To: <20171114224616.A6B8521C52@pdx-korg-gitolite-1.ci.codeaurora.org>
On Tue, Nov 14, 2017 at 10:46:16PM +0000, Linux Kernel Mailing List wrote:
> Web: https://git.kernel.org/torvalds/c/1d9ddde12e3c9bab7f3d3484eb9446315e3571ca
> Commit: 1d9ddde12e3c9bab7f3d3484eb9446315e3571ca
> Parent: 63c53823f00f0ffd13e8c86b05c1486614a2df85
> Refname: refs/heads/master
> Author: Eric Biggers <ebiggers@google.com>
> AuthorDate: Tue Nov 7 14:15:27 2017 -0800
> Committer: Herbert Xu <herbert@gondor.apana.org.au>
> CommitDate: Fri Nov 10 19:20:26 2017 +0800
>
> 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>
> ---
> lib/mpi/mpi-pow.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/mpi/mpi-pow.c b/lib/mpi/mpi-pow.c
> index e24388a863a7..468fb7cd1221 100644
> --- a/lib/mpi/mpi-pow.c
> +++ b/lib/mpi/mpi-pow.c
> @@ -26,6 +26,7 @@
> * however I decided to publish this code under the plain GPL.
> */
>
> +#include <linux/sched.h>
> #include <linux/string.h>
> #include "mpi-internal.h"
> #include "longlong.h"
> @@ -256,6 +257,7 @@ int mpi_powm(MPI res, MPI base, MPI exp, MPI mod)
> }
> e <<= 1;
> c--;
> + cond_resched();
> }
>
> i--;
Note, I've applied this to kernels older than 4.12 as well, as the issue
seems to also be there as well, right?
thanks,
greg k-h
next parent reply other threads:[~2017-11-27 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171114224616.A6B8521C52@pdx-korg-gitolite-1.ci.codeaurora.org>
2017-11-27 12:13 ` Greg KH [this message]
2017-11-27 18:24 ` lib/mpi: call cond_resched() from mpi_powm() loop Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171127121305.GB28339@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.