[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<168728881968.9715.9390991093529503679.git-patchwork-notify@kernel.org>
Date: Tue, 20 Jun 2023 19:20:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Howells <dhowells@...hat.com>
Cc: netdev@...r.kernel.org, herbert@...dor.apana.org.au,
syzbot+13a08c0bf4d212766c3c@...kaller.appspotmail.com,
syzbot+14234ccf6d0ef629ec1a@...kaller.appspotmail.com,
syzbot+4e2e47f32607d0f72d43@...kaller.appspotmail.com,
syzbot+472626bb5e7c59fb768f@...kaller.appspotmail.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, axboe@...nel.dk,
willy@...radead.org, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] crypto: af_alg/hash: Fix recvmsg() after
sendmsg(MSG_MORE)
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 16 Jun 2023 12:10:32 +0100 you wrote:
> If an AF_ALG socket bound to a hashing algorithm is sent a zero-length
> message with MSG_MORE set and then recvmsg() is called without first
> sending another message without MSG_MORE set to end the operation, an oops
> will occur because the crypto context and result doesn't now get set up in
> advance because hash_sendmsg() now defers that as long as possible in the
> hope that it can use crypto_ahash_digest() - and then because the message
> is zero-length, it the data wrangling loop is skipped.
>
> [...]
Here is the summary with links:
- [net-next,v2] crypto: af_alg/hash: Fix recvmsg() after sendmsg(MSG_MORE)
https://git.kernel.org/netdev/net-next/c/b6d972f68983
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists