tls: separate no-async decryption request handling from async
authorSabrina Dubroca <sd@queasysnail.net>
Wed, 28 Feb 2024 22:43:59 +0000 (23:43 +0100)
committerJakub Kicinski <kuba@kernel.org>
Thu, 29 Feb 2024 17:07:16 +0000 (09:07 -0800)
commit41532b785e9d79636b3815a64ddf6a096647d011
treedf26ff713718d54e616ada4c47a1abbec90fb8fd
parent6caaf104423d809b49a67ee6500191d063b40dc6
tls: separate no-async decryption request handling from async

If we're not doing async, the handling is much simpler. There's no
reference counting, we just need to wait for the completion to wake us
up and return its result.

We should preferably also use a separate crypto_wait. I'm not seeing a
UAF as I did in the past, I think aec7961916f3 ("tls: fix race between
async notify and socket close") took care of it.

This will make the next fix easier.

Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Link: https://lore.kernel.org/r/47bde5f649707610eaef9f0d679519966fc31061.1709132643.git.sd@queasysnail.net
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
net/tls/tls_sw.c