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, linux-afs@lists.infradead.org,
	marc.dionne@auristor.com, eiichi.tsukata@nutanix.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] rxrpc: Leak fixes
Date: Tue, 30 Nov 2021 04:20:11 +0000	[thread overview]
Message-ID: <163824601119.29763.1146825132755537453.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <163820097905.226370.17234085194655347888.stgit@warthog.procyon.org.uk>

Hello:

This series was applied to netdev/net.git (master)
by David Howells <dhowells@redhat.com>:

On Mon, 29 Nov 2021 15:49:39 +0000 you wrote:
> Here are a couple of fixes for leaks in AF_RXRPC:
> 
>  (1) Fix a leak of rxrpc_peer structs in rxrpc_look_up_bundle().
> 
>  (2) Fix a leak of rxrpc_local structs in rxrpc_lookup_peer().
> 
> The patches are tagged here:
> 
> [...]

Here is the summary with links:
  - [net,1/2] rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle()
    https://git.kernel.org/netdev/net/c/ca77fba82135
  - [net,2/2] rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer()
    https://git.kernel.org/netdev/net/c/beacff50edbd

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



      parent reply	other threads:[~2021-11-30  4:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 15:49 [PATCH net 0/2] rxrpc: Leak fixes David Howells
2021-11-29 15:49 ` [PATCH net 1/2] rxrpc: Fix rxrpc_peer leak in rxrpc_look_up_bundle() David Howells
2021-11-29 15:49 ` [PATCH net 2/2] rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() David Howells
2021-11-30  4:20 ` 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=163824601119.29763.1146825132755537453.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=eiichi.tsukata@nutanix.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    /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