summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorHerbert Xu <herbert@gondor.apana.org.au>2020-08-27 17:14:36 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-09-03 11:27:05 +0200
commit70957a10e1dbc72382994a8c630b7a0c0b55b515 (patch)
treee12d2328193f2adec3ddfacad036dcf65ce94950 /kernel
parentaca10ab0568aeb784b2ff47ca611e0fdc0c7f241 (diff)
downloadlinux-stable-70957a10e1dbc72382994a8c630b7a0c0b55b515.tar.gz
linux-stable-70957a10e1dbc72382994a8c630b7a0c0b55b515.tar.bz2
linux-stable-70957a10e1dbc72382994a8c630b7a0c0b55b515.zip
crypto: af_alg - Work around empty control messages without MSG_MORE
commit c195d66a8a75c60515819b101975f38b7ec6577f upstream. The iwd daemon uses libell which sets up the skcipher operation with two separate control messages. As the first control message is sent without MSG_MORE, it is interpreted as an empty request. While libell should be fixed to use MSG_MORE where appropriate, this patch works around the bug in the kernel so that existing binaries continue to work. We will print a warning however. A separate issue is that the new kernel code no longer allows the control message to be sent twice within the same request. This restriction is obviously incompatible with what iwd was doing (first setting an IV and then sending the real control message). This patch changes the kernel so that this is explicitly allowed. Reported-by: Caleb Jorden <caljorden@hotmail.com> Fixes: f3c802a1f300 ("crypto: algif_aead - Only wake up when...") Cc: <stable@vger.kernel.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions