[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220221120833.2618733-1-clabbe@baylibre.com>
Date: Mon, 21 Feb 2022 12:08:28 +0000
From: Corentin Labbe <clabbe@...libre.com>
To: herbert@...dor.apana.org.au, jernej.skrabec@...il.com,
linus.walleij@...aro.org, narmstrong@...libre.com,
ulli.kroll@...glemail.com, wens@...e.org
Cc: linux-amlogic@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-sunxi@...ts.linux.dev,
Corentin Labbe <clabbe@...libre.com>
Subject: [PATCH 0/5] crypto: completion should be ran with BH disabled
Hello
This is the follow up of https://lore.kernel.org/lkml/Yd1SIHUNdLIvKhzz@Red/
and https://patchwork.kernel.org/project/linux-crypto/patch/20220127133332.4011509-1-clabbe@baylibre.com/
This serie fix all drivers which do not call completion with BH disabled
and add the check in crypto/engine asked by Herbert.
I have verified that this check does not generate warnings on all other crypto
hardware I got (omap, ccree, rockchip)
Regards
Corentin Labbe (5):
crypto: sun8i-ss: call finalize with bh disabled
crypto: sun8i-ce: call finalize with bh disabled
crypto: amlogic: call finalize with bh disabled
crypto: gemini: call finalize with bh disabled
crypto: engine: check if BH is disabled during completion
crypto/crypto_engine.c | 1 +
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c | 3 +++
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-hash.c | 3 +++
drivers/crypto/allwinner/sun8i-ss/sun8i-ss-cipher.c | 3 +++
drivers/crypto/allwinner/sun8i-ss/sun8i-ss-hash.c | 3 +++
drivers/crypto/amlogic/amlogic-gxl-cipher.c | 2 ++
drivers/crypto/gemini/sl3516-ce-cipher.c | 2 ++
7 files changed, 17 insertions(+)
--
2.34.1
Powered by blists - more mailing lists