summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorYi Yang <yiyang13@huawei.com>2024-10-15 02:09:35 +0000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-12-05 14:01:18 +0100
commit7ddab756f2de5b7b43c122ebebdf37f400fb2b6f (patch)
tree89c2e1c1b960afb021c1b5f098a4e4a78715fed7 /scripts/stackusage
parenta69ef9c0d461de790b436b57dc5352717c7d8642 (diff)
downloadlinux-7ddab756f2de5b7b43c122ebebdf37f400fb2b6f.tar.gz
linux-7ddab756f2de5b7b43c122ebebdf37f400fb2b6f.tar.bz2
linux-7ddab756f2de5b7b43c122ebebdf37f400fb2b6f.zip
crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY
[ Upstream commit 662f2f13e66d3883b9238b0b96b17886179e60e2 ] Since commit 8f4f68e788c3 ("crypto: pcrypt - Fix hungtask for PADATA_RESET"), the pcrypt encryption and decryption operations return -EAGAIN when the CPU goes online or offline. In alg_test(), a WARN is generated when pcrypt_aead_decrypt() or pcrypt_aead_encrypt() returns -EAGAIN, the unnecessary panic will occur when panic_on_warn set 1. Fix this issue by calling crypto layer directly without parallelization in that case. Fixes: 8f4f68e788c3 ("crypto: pcrypt - Fix hungtask for PADATA_RESET") Signed-off-by: Yi Yang <yiyang13@huawei.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions