[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173440143824.415501.3353560173014525806.git-patchwork-notify@kernel.org>
Date: Tue, 17 Dec 2024 02:10:38 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: David Howells <dhowells@...hat.com>
Cc: netdev@...r.kernel.org, marc.dionne@...istor.com, kuba@...nel.org,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
linux-afs@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] rxrpc: Fix ability to add more data to a call once
MSG_MORE deasserted
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Thu, 12 Dec 2024 21:04:22 +0000 you wrote:
> When userspace is adding data to an RPC call for transmission, it must pass
> MSG_MORE to sendmsg() if it intends to add more data in future calls to
> sendmsg(). Calling sendmsg() without MSG_MORE being asserted closes the
> transmission phase of the call (assuming sendmsg() adds all the data
> presented) and further attempts to add more data should be rejected.
>
> However, this is no longer the case. The change of call state that was
> previously the guard got bumped over to the I/O thread, which leaves a
> window for a repeat sendmsg() to insert more data. This previously went
> unnoticed, but the more recent patch that changed the structures behind the
> Tx queue added a warning:
>
> [...]
Here is the summary with links:
- [net-next] rxrpc: Fix ability to add more data to a call once MSG_MORE deasserted
https://git.kernel.org/netdev/net-next/c/ae4f89989479
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