public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, zdi-disclosures@trendmicro.com,
	marc.dionne@auristor.com, linux-afs@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-CAN-15975]
Date: Fri, 18 Nov 2022 12:10:15 +0000	[thread overview]
Message-ID: <166877341585.19277.2863856871968966029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <166860734864.2970191.10633905995607769951.stgit@warthog.procyon.org.uk>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 16 Nov 2022 14:02:28 +0000 you wrote:
> After rxrpc_unbundle_conn() has removed a connection from a bundle, it
> checks to see if there are any conns with available channels and, if not,
> removes and attempts to destroy the bundle.
> 
> Whilst it does check after grabbing client_bundles_lock that there are no
> connections attached, this races with rxrpc_look_up_bundle() retrieving the
> bundle, but not attaching a connection for the connection to be attached
> later.
> 
> [...]

Here is the summary with links:
  - [net] rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-CAN-15975]
    https://git.kernel.org/netdev/net/c/3bcd6c7eaa53

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-11-18 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 14:02 [PATCH net] rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-CAN-15975] David Howells
2022-11-18 12:10 ` patchwork-bot+netdevbpf [this message]

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=166877341585.19277.2863856871968966029.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=zdi-disclosures@trendmicro.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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