From: sashiko-bot@kernel.org
To: "Allison Henderson" <achender@kernel.org>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v10 06/13] net/rds: split connection destroy into quiesce and kref-governed free
Date: Sat, 17 Oct 2026 03:38:15 +0000 [thread overview]
Message-ID: <sashiko-outbox-175258@kernel.org> (raw)
In-Reply-To: <20261017032319.2563014-7-achender@kernel.org>
> From: Sharath Srinivasan <sharath.srinivasan@oracle.com>
>
> rds_conn_destroy() tears down the transport state and immediately
> frees the connection, along with its paths and its workqueues. This
> relies on the assumption (documented in the rds_conn_destroy()
> comments) that "no one else is referencing the connection", which "we
> can only ensure ... in the rmmod path". However, the callers stopped
> honoring that long ago. Today, connections are also destroyed on
> network namespace teardown (rds_tcp_kill_sock() and
> rds_loop_kill_conns()), and the following patches deliberately let a
> connection outlive the call.
>
> This leaves loose ends since references to these destroyed
> connections still exist. Sockets cache their connections in rs_conn,
> and congestion updates will walk the maps' m_conn_list. The CM
> [ ... ]
> infrastructure, no rds_net, single conn hash); destroy keeps its
> one-call external interface; holder coverage split out into follow-up
> patches; rewrite commit message]
> Assisted-by: Claude-Code:claude-fable-5
> Signed-off-by: Allison Henderson <achender@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261017032319.2563014-1-achender@kernel.org?part=6
next prev parent reply other threads:[~2026-10-17 3:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 3:23 [PATCH net-next v10 00/13] net/rds: make connection lifetime reference-counted Allison Henderson
2026-10-17 3:23 ` [PATCH net-next v10 01/13] net/rds: ib: don't enable interrupts in rds_ib_conn_free() Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 02/13] net/rds: undo conn_alloc() the same way on every __rds_conn_create() exit Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 03/13] net/rds: ib: refuse to attach a connection to a device being removed Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 04/13] net/rds: guard every work-requeueing site with rds_destroy_pending() Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 05/13] net/rds: make rds_destroy_pending() report a connection's own destroy Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 06/13] net/rds: split connection destroy into quiesce and kref-governed free Allison Henderson
2026-10-17 3:38 ` sashiko-bot [this message]
2026-10-17 3:23 ` [PATCH net-next v10 07/13] net/rds: unlink transport nodes before a possibly deferred connection free Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 08/13] net/rds: wait for connections to be freed on transport unload Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 09/13] net/rds: hold a connection reference from struct rds_incoming Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 10/13] net/rds: take cp_lock to purge cp_send_queue in the quiesce Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 11/13] net/rds: hold connection references in lookup, sockets and c_passive Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 12/13] net/rds: pin the connection across RDMA-CM event handling Allison Henderson
2026-10-17 3:38 ` sashiko-bot
2026-10-17 3:23 ` [PATCH net-next v10 13/13] net/rds: drop rds_conn_count in favor of t_conn_count Allison Henderson
2026-10-17 3:38 ` sashiko-bot
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=sashiko-outbox-175258@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=achender@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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