From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
horms@kernel.org, jhubbard@nvidia.com, woni9911@gmail.com,
michal.kubiak@intel.com, leon@kernel.org
Subject: Re: [PATCH net v5 0/7] net/rds: own the fastpath locks across connection teardown
Date: Thu, 03 Sep 2026 03:00:19 +0000 [thread overview]
Message-ID: <178840441963.3061644.9034056329969697998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260828223921.202913-1-achender@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Aug 2026 15:39:14 -0700 you wrote:
> Hi all,
>
> This is v5 of the follow-up set to "net/rds: Bug fix ports, part 2"
> [1] (v1 at [2], v2 at [3], v3 at [4], v4 at [5]). During review of part 2, the
> later half of that series needed more work than a respin, so it was
> split off into this set together with the companion fixes identified
> along the way. As discussed on the v2 thread, it is targeted at net.
>
> [...]
Here is the summary with links:
- [net,v5,1/7] net/rds: use wq_has_sleeper() in release_in_xmit()
https://git.kernel.org/netdev/net/c/6d0c8b707391
- [net,v5,2/7] net/rds: use clear_bit_unlock() in release_refill()
https://git.kernel.org/netdev/net/c/17c4476dbb9c
- [net,v5,3/7] net/rds: clear cp_flags bits individually in rds_conn_path_reset()
https://git.kernel.org/netdev/net/c/103c4b13c4f5
- [net,v5,4/7] net/rds: tcp: don't force RDS_CONN_RESETTING over a concurrent shutdown
https://git.kernel.org/netdev/net/c/e8e60d74fec4
- [net,v5,5/7] net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks()
https://git.kernel.org/netdev/net/c/02c5f9dc2efd
- [net,v5,6/7] net/rds: acquire the fastpath locks in rds_conn_shutdown()
https://git.kernel.org/netdev/net/c/813f3582ac7a
- [net,v5,7/7] net/rds: don't let rds_conn_shutdown() consume a concurrent drop
https://git.kernel.org/netdev/net/c/260c6308fe2e
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:[~2026-09-03 3:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 22:39 [PATCH net v5 0/7] net/rds: own the fastpath locks across connection teardown Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 1/7] net/rds: use wq_has_sleeper() in release_in_xmit() Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 2/7] net/rds: use clear_bit_unlock() in release_refill() Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 3/7] net/rds: clear cp_flags bits individually in rds_conn_path_reset() Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 4/7] net/rds: tcp: don't force RDS_CONN_RESETTING over a concurrent shutdown Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 5/7] net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 6/7] net/rds: acquire the fastpath locks in rds_conn_shutdown() Allison Henderson
2026-08-28 22:39 ` [PATCH net v5 7/7] net/rds: don't let rds_conn_shutdown() consume a concurrent drop Allison Henderson
2026-09-03 3: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=178840441963.3061644.9034056329969697998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woni9911@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