crypto: aesni - don't use GFP_ATOMIC allocation if the request doesn't cross a page...
authorMikulas Patocka <mpatocka@redhat.com>
Wed, 5 Sep 2018 13:18:43 +0000 (09:18 -0400)
committerHerbert Xu <herbert@gondor.apana.org.au>
Fri, 14 Sep 2018 06:08:53 +0000 (14:08 +0800)
commita788848116454d753b13a4888e0e31ada3c4d393
treea1578d1f658cb0f7a69cdf86f40321325c936881
parenta7e7edfea23fa1f3c910eac897aac41ec9584c38
crypto: aesni - don't use GFP_ATOMIC allocation if the request doesn't cross a page in gcm

This patch fixes gcmaes_crypt_by_sg so that it won't use memory
allocation if the data doesn't cross a page boundary.

Authenticated encryption may be used by dm-crypt. If the encryption or
decryption fails, it would result in I/O error and filesystem corruption.
The function gcmaes_crypt_by_sg is using GFP_ATOMIC allocation that can
fail anytime. This patch fixes the logic so that it won't attempt the
failing allocation if the data doesn't cross a page boundary.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Cc: stable@vger.kernel.org
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
arch/x86/crypto/aesni-intel_glue.c