From: sashiko-bot@kernel.org
To: "Chuck Lever" <cel@kernel.org>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH 2/5] svcrdma: drop the extra reference on the backchannel transport
Date: Wed, 04 Nov 2026 18:03:48 +0000 [thread overview]
Message-ID: <sashiko-outbox-197812@kernel.org> (raw)
In-Reply-To: <20261104-liange-v1-2-f097e10cea1b@kernel.org>
> From: Wentao Liang <vulab@iscas.ac.cn>
>
> Beyond the reference xprt_alloc() returns to the caller,
> xprt_setup_rdma_bc() takes two more on the new rpc_xprt: one for the
> xpt_bc_xprt link, which svc_xprt_free() drops, and a second whose put
> was in __svc_rdma_free(). Commit 729580ddc53e ("svcrdma: xpt_bc_xprt
> is already clear in __svc_rdma_free()") removed that put as a
> duplicate of the one in svc_xprt_free(), but left the matching
> xprt_get() in place. The second reference is therefore never
> released: the rpc_xprt outlives the callback client and the
> connection, and the net namespace reference taken by xprt_alloc()
> leaks along with the rpc_xprt.
>
> Take only the reference that svc_xprt_free() releases, as
> xs_setup_bc_tcp() does.
>
> Fixes: 729580ddc53e ("svcrdma: xpt_bc_xprt is already clear in __svc_rdma_free()")
> Cc: stable@vger.kernel.org
> Assisted-by: DeepSeek-V4.1-Flash and OpenAI Codex
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> Link: https://patch.msgid.link/20261104022813.1484267-1-vulab@iscas.ac.cn
> Signed-off-by: Chuck Lever <cel@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261104-liange-v1-0-f097e10cea1b@kernel.org?part=2
next prev parent reply other threads:[~2026-11-04 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 17:49 [PATCH 0/5] SUNRPC: Fix backchannel transport lifetime bugs Chuck Lever
2026-11-04 17:49 ` [PATCH 1/5] SUNRPC: Reject add_xprt on a backchannel xprt_switch Chuck Lever
2026-11-04 17:59 ` sashiko-bot
2026-11-04 17:49 ` [PATCH 2/5] svcrdma: drop the extra reference on the backchannel transport Chuck Lever
2026-11-04 18:03 ` sashiko-bot [this message]
2026-11-04 17:49 ` [PATCH 3/5] svcrdma: Hold a module reference for " Chuck Lever
2026-11-04 18:04 ` sashiko-bot
2026-11-04 17:49 ` [PATCH 4/5] svcrdma: Set xprt_class on " Chuck Lever
2026-11-04 17:53 ` sashiko-bot
2026-11-04 17:49 ` [PATCH 5/5] SUNRPC: Set up the servername before the transport is created Chuck Lever
2026-11-04 17:54 ` 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-197812@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.