From: patchwork-bot+netdevbpf@kernel.org
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
Subject: Re: [PATCH net] rxrpc: Fix locking in rxrpc's sendmsg
Date: Thu, 25 Aug 2022 20:00:17 +0000 [thread overview]
Message-ID: <166145761774.4210.6304609883412894569.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <166135894583.600315.7170979436768124075.stgit@warthog.procyon.org.uk>
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
prev parent reply other threads:[~2022-08-25 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 16:35 [PATCH net] rxrpc: Fix locking in rxrpc's sendmsg David Howells
2022-08-25 20:00 ` 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=166145761774.4210.6304609883412894569.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=dhowells@redhat.com \
--cc=khalid.masum.92@gmail.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+7f0483225d0c94cb3441@syzkaller.appspotmail.com \
--cc=yin31149@gmail.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