From: sashiko-bot@kernel.org
To: "Chuck Lever" <cel@kernel.org>
Cc: linux-rdma@vger.kernel.org, "Chuck Lever" <cel@kernel.org>,
"Jeff Layton" <jlayton@kernel.org>,
"Anna Schumaker" <anna@kernel.org>
Subject: Re: [PATCH v1 4/5] svcrdma: release a send context stranded by a partial post
Date: Tue, 22 Sep 2026 01:59:56 +0000 [thread overview]
Message-ID: <20260922015956.D7A481F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260922015128.240977-4-cel@kernel.org>
> When ib_post_send() rejects a WR mid-chain, svc_rdma_post_send_err()
> returns zero to say that a completion will clean up. The Write and
> Reply chunk WRs in a reply's chain do carry completions, but those
> only trace or close the transport. The Send at the chain's tail is
> the one whose completion puts the send context, so a chain cut
> before the Send leaves the context unreleased. svc_rdma_sendto()
> reports success and never puts it either. No list the transport
> destructor walks holds the context, so it leaks past teardown along
> with the DMA mappings, page references, and rw contexts it owns.
>
> The error path cannot release the context itself. The posted WRs
> still reference its rw contexts and pages, and the HCA may still be
> reading them. Nor can it drain the Send Queue to wait for them. A
> drain needs a free SQ slot for its marker WR. A provider that
> rejects a WR after accepting earlier ones has most likely diverged
> [ ... ]
> contract. The chain became long enough to cut only with commit
> 10e6fc1054d9 ("svcrdma: Post the Reply chunk and Send WR together").
>
> Fixes: 71b43531ee0b ("svcrdma: Post Send WR chain")
> Signed-off-by: Chuck Lever <cel@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260922015128.240977-1-cel@kernel.org?part=4
next prev parent reply other threads:[~2026-09-22 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 1:51 [PATCH v1 1/5] SUNRPC: fire svc_xprt_free tracepoint before dropping the netns Chuck Lever
2026-09-22 1:51 ` [PATCH v1 2/5] SUNRPC: fire svc_defer_queue tracepoint before publishing the request Chuck Lever
2026-09-22 1:57 ` sashiko-bot
2026-09-22 1:51 ` [PATCH v1 3/5] svcrdma: fix a page leak in backchannel sends Chuck Lever
2026-09-22 1:58 ` sashiko-bot
2026-09-22 1:51 ` [PATCH v1 4/5] svcrdma: release a send context stranded by a partial post Chuck Lever
2026-09-22 1:59 ` sashiko-bot [this message]
2026-09-22 1:51 ` [PATCH v1 5/5] svcrdma: release a receive context stranded by a partial Read post Chuck Lever
2026-09-22 1:57 ` sashiko-bot
2026-09-22 1:57 ` [PATCH v1 1/5] SUNRPC: fire svc_xprt_free tracepoint before dropping the netns 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=20260922015956.D7A481F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@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