From: Jason Gunthorpe <jgg@nvidia.com>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org, shiraz.saleem@intel.com,
mustafa.ismail@intel.com, leon@kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH V6] RDMA/irdma: Fix deadlock in irdma_cleanup_cm_core()
Date: Tue, 19 Apr 2022 13:13:51 -0300 [thread overview]
Message-ID: <20220419161351.GA1245221@nvidia.com> (raw)
In-Reply-To: <20220418153322.42524-1-duoming@zju.edu.cn>
On Mon, Apr 18, 2022 at 11:33:22PM +0800, Duoming Zhou wrote:
> There is a deadlock in irdma_cleanup_cm_core(), which is shown
> below:
>
> (Thread 1) | (Thread 2)
> | irdma_schedule_cm_timer()
> irdma_cleanup_cm_core() | add_timer()
> spin_lock_irqsave() //(1) | (wait a time)
> ... | irdma_cm_timer_tick()
> del_timer_sync() | spin_lock_irqsave() //(2)
> (wait timer to stop) | ...
>
> We hold cm_core->ht_lock in position (1) of thread 1 and
> use del_timer_sync() to wait timer to stop, but timer handler
> also need cm_core->ht_lock in position (2) of thread 2.
> As a result, irdma_cleanup_cm_core() will block forever.
>
> This patch removes the check of timer_pending() in
> irdma_cleanup_cm_core(), because the del_timer_sync()
> function will just return directly if there isn't a
> pending timer. As a result, the lock is redundant,
> because there is no resource it could protect.
>
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> ---
> Changes in V6:
> - Change subject line prefixed with "RDMA/irdma: ".
>
> drivers/infiniband/hw/irdma/cm.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
I fixed the compile warning.
Applied to for-rc, thanks
Jason
prev parent reply other threads:[~2022-04-19 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 15:33 [PATCH V6] RDMA/irdma: Fix deadlock in irdma_cleanup_cm_core() Duoming Zhou
2022-04-19 16:13 ` Jason Gunthorpe [this message]
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=20220419161351.GA1245221@nvidia.com \
--to=jgg@nvidia.com \
--cc=duoming@zju.edu.cn \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=shiraz.saleem@intel.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