From: Ye Bin <yebin@huaweicloud.com>
To: ericvh@gmail.com, lucho@ionkov.net, asmadeus@codewreck.org,
linux_oss@crudebyte.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
v9fs-developer@lists.sourceforge.net, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yebin10@huawei.com
Subject: [PATCH 2/5] 9p: fix miss release semaphore in 'rdma_request()'
Date: Mon, 21 Nov 2022 16:00:46 +0800 [thread overview]
Message-ID: <20221121080049.3850133-3-yebin@huaweicloud.com> (raw)
In-Reply-To: <20221121080049.3850133-1-yebin@huaweicloud.com>
From: Ye Bin <yebin10@huawei.com>
If send request failed will not call 'send_done()', but already get
'(&rdma->sq_sem'. So add release '(&rdma->sq_sem' after send request failed.
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
net/9p/trans_rdma.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/net/9p/trans_rdma.c b/net/9p/trans_rdma.c
index e498208ed72b..ae2bac9bf510 100644
--- a/net/9p/trans_rdma.c
+++ b/net/9p/trans_rdma.c
@@ -509,8 +509,10 @@ static int rdma_request(struct p9_client *client, struct p9_req_t *req)
*/
req->status = REQ_STATUS_SENT;
err = ib_post_send(rdma->qp, &wr, NULL);
- if (err)
+ if (err) {
+ up(&rdma->sq_sem);
goto mapping_error;
+ }
/* Success */
return 0;
--
2.31.1
next prev parent reply other threads:[~2022-11-21 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 8:00 [PATCH 0/5] Fix error handle in 'rdma_request()' Ye Bin
2022-11-21 8:00 ` [PATCH 1/5] 9p: fix miss unmap request " Ye Bin
2022-11-21 8:00 ` Ye Bin [this message]
2022-11-21 8:00 ` [PATCH 3/5] 9p: fix error handle in 'post_recv()' Ye Bin
2022-11-21 8:00 ` [PATCH 4/5] 9p: factor out 'post_send()' Ye Bin
2022-11-21 8:00 ` [PATCH 5/5] 9p: refactor 'post_recv()' Ye Bin
2022-11-22 0:27 ` [PATCH 0/5] Fix error handle in 'rdma_request()' asmadeus
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=20221121080049.3850133-3-yebin@huaweicloud.com \
--to=yebin@huaweicloud.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=yebin10@huawei.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).