Hello:
This series was applied to bpf/bpf-next.git (master) by Arnaldo Carvalho de Melo acme@redhat.com:
On Mon, 15 May 2023 18:23:54 +0200 you wrote:
From: David Howells dhowells@redhat.com
[ Upstream commit 2b5fdc0f5caa505afe34d608e2eefadadf2ee67a ]
Inside the loop in rxrpc_wait_to_be_connected() it checks call->error to see if it should exit the loop without first checking the call state. This is probably safe as if call->error is set, the call is dead anyway, but we should probably wait for the call state to have been set to completion first, lest it cause surprise on the way out.
[...]
Here is the summary with links: - [6.3,022/246] rxrpc: Fix potential data race in rxrpc_wait_to_be_connected() (no matching commit) - [6.3,051/246] rxrpc: Fix hard call timeout units (no matching commit) - [6.3,052/246] rxrpc: Make it so that a waiting process can be aborted (no matching commit) - [6.3,053/246] rxrpc: Fix timeout of a call that hasnt yet been granted a channel (no matching commit) - [6.3,100/246] perf lock contention: Fix compiler builtin detection https://git.kernel.org/bpf/bpf-next/c/17535a33a9c1
You are awesome, thank you!