From: Taehee Yoo <ap420073@gmail.com>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, ardb@kernel.org, ebiggers@google.com
Cc: ap420073@gmail.com
Subject: [PATCH] crypto: x86: Do not acquire fpu context for too long
Date: Tue, 4 Oct 2022 04:49:12 +0000 [thread overview]
Message-ID: <20221004044912.24770-1-ap420073@gmail.com> (raw)
Many drivers such as camellia, cast5, etc are using ECB macro.
ECB macro internally calls kernel_fpu_begin() then calls encrypt()
and decrypt() and then it calls kernel_fpu_end().
If too many blocks are given, it acquires fpu context for too long.
kernel_fpu_{begin | end}() internally calls preempt_{disable | enable}().
So, RCU stall would occur because of too long FPU context
period.
The purpose of this is to not exceed 4096 bytes to encrypt() and
decrypt() in an FPU context.
Fixes: 827ee47228a6 ("crypto: x86 - add some helper macros for ECB and CBC modes")
Suggested-by: Elliott, Robert (Servers) <elliott@hpe.com>
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
---
arch/x86/crypto/ecb_cbc_helpers.h | 34 ++++++++++++++++++++++++-------
1 file changed, 27 insertions(+), 7 deletions(-)
diff --git a/arch/x86/crypto/ecb_cbc_helpers.h b/arch/x86/crypto/ecb_cbc_helpers.h
index eaa15c7b29d6..551d8bdfd037 100644
--- a/arch/x86/crypto/ecb_cbc_helpers.h
+++ b/arch/x86/crypto/ecb_cbc_helpers.h
@@ -11,19 +11,35 @@
* having to rely on indirect calls and retpolines.
*/
+#define ECB_CBC_WALK_MAX 4096
+
#define ECB_WALK_START(req, bsize, fpu_blocks) do { \
void *ctx = crypto_skcipher_ctx(crypto_skcipher_reqtfm(req)); \
+ unsigned int walked_bytes = 0; \
const int __bsize = (bsize); \
struct skcipher_walk walk; \
- int err = skcipher_walk_virt(&walk, (req), false); \
+ int err; \
+ \
+ err = skcipher_walk_virt(&walk, (req), false); \
while (walk.nbytes > 0) { \
- unsigned int nbytes = walk.nbytes; \
- bool do_fpu = (fpu_blocks) != -1 && \
- nbytes >= (fpu_blocks) * __bsize; \
const u8 *src = walk.src.virt.addr; \
- u8 *dst = walk.dst.virt.addr; \
u8 __maybe_unused buf[(bsize)]; \
- if (do_fpu) kernel_fpu_begin()
+ u8 *dst = walk.dst.virt.addr; \
+ unsigned int nbytes; \
+ bool do_fpu; \
+ \
+ if (walk.nbytes - walked_bytes > ECB_CBC_WALK_MAX) { \
+ nbytes = ECB_CBC_WALK_MAX; \
+ walked_bytes += ECB_CBC_WALK_MAX; \
+ } else { \
+ nbytes = walk.nbytes - walked_bytes; \
+ walked_bytes = walk.nbytes; \
+ } \
+ \
+ do_fpu = (fpu_blocks) != -1 && \
+ nbytes >= (fpu_blocks) * __bsize; \
+ if (do_fpu) \
+ kernel_fpu_begin()
#define CBC_WALK_START(req, bsize, fpu_blocks) \
ECB_WALK_START(req, bsize, fpu_blocks)
@@ -65,8 +81,12 @@
} while (0)
#define ECB_WALK_END() \
- if (do_fpu) kernel_fpu_end(); \
+ if (do_fpu) \
+ kernel_fpu_end(); \
+ if (walked_bytes < walk.nbytes) \
+ continue; \
err = skcipher_walk_done(&walk, nbytes); \
+ walked_bytes = 0; \
} \
return err; \
} while (0)
--
2.17.1
next reply other threads:[~2022-10-04 4:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 4:49 Taehee Yoo [this message]
2022-10-04 4:52 ` [PATCH] crypto: x86: Do not acquire fpu context for too long Herbert Xu
2022-10-04 6:01 ` Taehee Yoo
2022-10-04 15:16 ` Elliott, Robert (Servers)
2022-10-07 21:54 ` Ard Biesheuvel
2022-10-08 19:48 ` Elliott, Robert (Servers)
2022-10-09 6:19 ` Herbert Xu
2022-10-09 19:58 ` Elliott, Robert (Servers)
2022-10-11 15:16 ` Elliott, Robert (Servers)
2022-10-12 6:08 ` Taehee Yoo
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=20221004044912.24770-1-ap420073@gmail.com \
--to=ap420073@gmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox