Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net] rxrpc: Fix locking in rxrpc's sendmsg
From:   patchwork-bot+netdevbpf@kernel.org
Message-Id: <166145761774.4210.6304609883412894569.git-patchwork-notify@kernel.org>
Date:   Thu, 25 Aug 2022 20:00:17 +0000
References: <166135894583.600315.7170979436768124075.stgit@warthog.procyon.org.uk>
In-Reply-To: <166135894583.600315.7170979436768124075.stgit@warthog.procyon.org.uk>
To:     David Howells <dhowells@redhat.com>
Cc:     netdev@vger.kernel.org,
        syzbot+7f0483225d0c94cb3441@syzkaller.appspotmail.com,
        marc.dionne@auristor.com, yin31149@gmail.com,
        khalid.masum.92@gmail.com, dan.carpenter@oracle.com,
        linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Precedence: bulk

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 24 Aug 2022 17:35:45 +0100 you wrote:
> Fix three bugs in the rxrpc's sendmsg implementation:
> 
>  (1) rxrpc_new_client_call() should release the socket lock when returning
>      an error from rxrpc_get_call_slot().
> 
>  (2) rxrpc_wait_for_tx_window_intr() will return without the call mutex
>      held in the event that we're interrupted by a signal whilst waiting
>      for tx space on the socket or relocking the call mutex afterwards.
> 
> [...]

Here is the summary with links:
  - [net] rxrpc: Fix locking in rxrpc's sendmsg
    https://git.kernel.org/netdev/net/c/b0f571ecd794

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