From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, davem@davemloft.net,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc, afs: Fix peer hash locking vs RCU callback
Date: Mon, 27 Jan 2025 23:10:41 +0000 [thread overview]
Message-ID: <173801944199.3253418.8964414973990474171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2095618.1737622752@warthog.procyon.org.uk>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 23 Jan 2025 08:59:12 +0000 you wrote:
> In its address list, afs now retains pointers to and refs on one or more
> rxrpc_peer objects. The address list is freed under RCU and at this time,
> it puts the refs on those peers.
>
> Now, when an rxrpc_peer object runs out of refs, it gets removed from the
> peer hash table and, for that, rxrpc has to take a spinlock. However, it
> is now being called from afs's RCU cleanup, which takes place in BH
> context - but it is just taking an ordinary spinlock.
>
> [...]
Here is the summary with links:
- [net] rxrpc, afs: Fix peer hash locking vs RCU callback
https://git.kernel.org/netdev/net/c/79d458c13056
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:[~2025-01-27 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 8:59 [PATCH net] rxrpc, afs: Fix peer hash locking vs RCU callback David Howells
2025-01-27 23: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=173801944199.3253418.8964414973990474171.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).