From: Dan Carpenter <dan.carpenter@oracle.com>
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-kernel@vger.kernel.org, chris@zankel.net,
jcmvbkbc@gmail.com, mustafa.ismail@intel.com,
shiraz.saleem@intel.com, jgg@ziepe.ca, wg@grandegger.com,
mkl@pengutronix.de, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, jes@trained-monkey.org,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
alexander.deucher@amd.com, linux-xtensa@linux-xtensa.org,
linux-rdma@vger.kernel.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-hippi@sunsite.dk,
linux-staging@lists.linux.dev, linux-serial@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 09/11] drivers: infiniband: hw: Fix deadlock in irdma_cleanup_cm_core()
Date: Thu, 7 Apr 2022 14:24:56 +0300 [thread overview]
Message-ID: <20220407112455.GK3293@kadam> (raw)
In-Reply-To: <4069b99042d28c8e51b941d9e698b99d1656ed33.1649310812.git.duoming@zju.edu.cn>
On Thu, Apr 07, 2022 at 02:37:12PM +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 extracts del_timer_sync() from the protection of
> spin_lock_irqsave(), which could let timer handler to obtain
> the needed lock.
>
> Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> ---
> drivers/infiniband/hw/irdma/cm.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/irdma/cm.c b/drivers/infiniband/hw/irdma/cm.c
> index dedb3b7edd8..019dd8bfe08 100644
> --- a/drivers/infiniband/hw/irdma/cm.c
> +++ b/drivers/infiniband/hw/irdma/cm.c
> @@ -3252,8 +3252,11 @@ void irdma_cleanup_cm_core(struct irdma_cm_core *cm_core)
> return;
>
> spin_lock_irqsave(&cm_core->ht_lock, flags);
> - if (timer_pending(&cm_core->tcp_timer))
> + if (timer_pending(&cm_core->tcp_timer)) {
> + spin_unlock_irqrestore(&cm_core->ht_lock, flags);
> del_timer_sync(&cm_core->tcp_timer);
> + spin_lock_irqsave(&cm_core->ht_lock, flags);
> + }
> spin_unlock_irqrestore(&cm_core->ht_lock, flags);
This lock doesn't seem to be protecting anything. Also do we need to
check timer_pending()? I think the del_timer_sync() function will just
return directly if there isn't a pending lock?
regards,
dan carpenter
next prev parent reply other threads:[~2022-04-07 11:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 6:33 [PATCH 00/11] Fix deadlocks caused by del_timer_sync() Duoming Zhou
2022-04-07 6:33 ` [PATCH 01/11] drivers: tty: serial: Fix deadlock in sa1100_set_termios() Duoming Zhou
2022-04-07 7:02 ` Jiri Slaby
2022-04-07 14:03 ` duoming
2022-04-07 6:33 ` [PATCH 02/11] drivers: usb: host: Fix deadlock in oxu_bus_suspend() Duoming Zhou
2022-04-07 8:01 ` Oliver Neukum
2022-04-07 12:02 ` duoming
2022-04-07 6:33 ` [PATCH 03/11] drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop() Duoming Zhou
2022-04-07 6:33 ` [PATCH 04/11] drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() Duoming Zhou
2022-04-07 6:36 ` [PATCH 05/11] drivers: staging: rtl8192e: Fix deadlock in rtllib_beacons_stop() Duoming Zhou
2022-04-07 6:36 ` [PATCH 06/11] drivers: staging: rtl8192e: Fix deadlock in rtw_joinbss_event_prehandle() Duoming Zhou
2022-04-07 6:36 ` [PATCH 07/11] drivers: net: hippi: Fix deadlock in rr_close() Duoming Zhou
2022-04-07 6:37 ` [PATCH 08/11] drivers: net: can: Fix deadlock in grcan_close() Duoming Zhou
2022-04-07 6:37 ` [PATCH 09/11] drivers: infiniband: hw: Fix deadlock in irdma_cleanup_cm_core() Duoming Zhou
2022-04-07 11:24 ` Dan Carpenter [this message]
2022-04-07 12:54 ` duoming
2022-04-07 14:23 ` Jason Gunthorpe
2022-04-07 14:38 ` duoming
2022-04-07 17:35 ` Saleem, Shiraz
2022-04-07 15:24 ` Dan Carpenter
2022-04-07 17:36 ` Saleem, Shiraz
2022-04-08 0:35 ` duoming
2022-04-08 2:21 ` Saleem, Shiraz
2022-04-08 2:52 ` duoming
2022-04-07 6:37 ` [PATCH 10/11] arch: xtensa: platforms: Fix deadlock in iss_net_close() Duoming Zhou
2022-04-07 6:37 ` [PATCH 11/11] arch: xtensa: platforms: Fix deadlock in rs_close() Duoming Zhou
2022-04-07 7:21 ` Max Filippov
2022-04-07 11:05 ` duoming
2022-04-07 9:42 ` Sergey Shtylyov
2022-04-07 11:12 ` duoming
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=20220407112455.GK3293@kadam \
--to=dan.carpenter@oracle.com \
--cc=alexander.deucher@amd.com \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=duoming@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=jes@trained-monkey.org \
--cc=jgg@ziepe.ca \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-hippi@sunsite.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-usb@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=mkl@pengutronix.de \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shiraz.saleem@intel.com \
--cc=wg@grandegger.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).