public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Greg KH <gregkh@linuxfoundation•org>
Cc: stable@vger•kernel.org, patches@lists•linux.dev,
	syzbot+ebc945fdb4acd72cba78@syzkaller•appspotmail.com,
	dhowells@redhat•com, marc.dionne@auristor•com,
	dvyukov@google•com, davem@davemloft•net, edumazet@google•com,
	kuba@kernel•org, pabeni@redhat•com,
	linux-afs@lists•infradead.org, linux-fsdevel@vger•kernel.org,
	netdev@vger•kernel.org, sashal@kernel•org
Subject: Re: [PATCH 6.3 022/246] rxrpc: Fix potential data race in rxrpc_wait_to_be_connected()
Date: Wed, 17 May 2023 03:38:02 +0000	[thread overview]
Message-ID: <168429468203.3680.17732082530948499467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230515161723.275161336@linuxfoundation.org>

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!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2023-05-17  3:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230515161722.610123835@linuxfoundation.org>
2023-05-15 16:23 ` [PATCH 6.3 022/246] rxrpc: Fix potential data race in rxrpc_wait_to_be_connected() Greg Kroah-Hartman
2023-05-17  3:38   ` patchwork-bot+netdevbpf [this message]
2023-05-15 16:24 ` [PATCH 6.3 051/246] rxrpc: Fix hard call timeout units Greg Kroah-Hartman
2023-05-15 16:24 ` [PATCH 6.3 052/246] rxrpc: Make it so that a waiting process can be aborted Greg Kroah-Hartman
2023-05-15 16:24 ` [PATCH 6.3 053/246] rxrpc: Fix timeout of a call that hasnt yet been granted a channel Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=168429468203.3680.17732082530948499467.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dhowells@redhat$(echo .)com \
    --cc=dvyukov@google$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-afs@lists$(echo .)infradead.org \
    --cc=linux-fsdevel@vger$(echo .)kernel.org \
    --cc=marc.dionne@auristor$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=patches@lists$(echo .)linux.dev \
    --cc=sashal@kernel$(echo .)org \
    --cc=stable@vger$(echo .)kernel.org \
    --cc=syzbot+ebc945fdb4acd72cba78@syzkaller$(echo .)appspotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox