[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<168429468203.3680.17732082530948499467.git-patchwork-notify@kernel.org>
Date: Wed, 17 May 2023 03:38:02 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Greg KH <gregkh@...uxfoundation.org>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
syzbot+ebc945fdb4acd72cba78@...kaller.appspotmail.com, dhowells@...hat.com,
marc.dionne@...istor.com, dvyukov@...gle.com, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
linux-afs@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
netdev@...r.kernel.org, sashal@...nel.org
Subject: Re: [PATCH 6.3 022/246] rxrpc: Fix potential data race in
rxrpc_wait_to_be_connected()
Hello:
This series was applied to bpf/bpf-next.git (master)
by Arnaldo Carvalho de Melo <acme@...hat.com>:
On Mon, 15 May 2023 18:23:54 +0200 you wrote:
> From: David Howells <dhowells@...hat.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!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists