From: Philipp Reisner <philipp.reisner@linbit.com>
To: "zhengbing . huang" <zhengbing.huang@easystack.cn>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [PATCH] rdma: Fix cm leak
Date: Mon, 5 May 2025 16:26:22 +0200 [thread overview]
Message-ID: <20250505142623.424049-1-philipp.reisner@linbit.com> (raw)
In-Reply-To: <20250425102421.1673048-1-zhengbing.huang@easystack.cn>
Hi Zhengbing,
Yes, I agree. I follow your explanation of what happened and your
proposed fix. I think we also need to clear the DSB_CONNECT_REQ bit in
the RDMA_CM_EVENT_ESTABLISHED case.
Please see my proposal, which is slightly modified from your original
patch.
Best regards,
Philipp
zhengbing.huang (1):
rdma: Fix cm leak
drbd/drbd_transport_rdma.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
--
2.49.0
next prev parent reply other threads:[~2025-05-05 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:24 [PATCH] rdma: Fix cm leak zhengbing.huang
2025-05-05 14:26 ` Philipp Reisner [this message]
2025-05-06 2:20 ` ZhengbingHuang
2025-05-05 14:26 ` [PATCH 1/1] " Philipp Reisner
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=20250505142623.424049-1-philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=zhengbing.huang@easystack.cn \
/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