From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: kgraul@linux.ibm.com, davem@davemloft.net, kuba@kernel.org
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] net: smc: possible deadlock in smc_lgr_free() and smc_link_down_work()
Date: Tue, 1 Feb 2022 15:51:30 +0800 [thread overview]
Message-ID: <11fe65b8-eda4-121e-ec32-378b918d0909@gmail.com> (raw)
Hello,
My static analysis tool reports a possible deadlock in the smc module in
Linux 5.16:
smc_lgr_free()
mutex_lock(&lgr->llc_conf_mutex); --> Line 1289 (Lock A)
smcr_link_clear()
smc_wr_free_link()
wait_event(lnk->wr_tx_wait, ...); --> Line 648 (Wait X)
smc_link_down_work()
mutex_lock(&lgr->llc_conf_mutex); --> Line 1683 (Lock A)
smcr_link_down()
smcr_link_clear()
smc_wr_free_link()
smc_wr_wakeup_tx_wait()
wake_up_all(&lnk->wr_tx_wait); --> Line 78 (Wake X)
When smc_lgr_free() is executed, "Wait X" is performed by holding "Lock
A". If smc_link_down_work() is executed at this time, "Wake X" cannot be
performed to wake up "Wait X" in smc_lgr_free(), because "Lock A" has
been already hold by smc_lgr_free(), causing a possible deadlock.
I am not quite sure whether this possible problem is real and how to fix
it if it is real.
Any feedback would be appreciated, thanks :)
Best wishes,
Jia-Ju Bai
next reply other threads:[~2022-02-01 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 7:51 Jia-Ju Bai [this message]
2022-02-01 10:53 ` [BUG] net: smc: possible deadlock in smc_lgr_free() and smc_link_down_work() Karsten Graul
2022-02-01 17:06 ` Karsten Graul
2022-02-06 15:09 ` Jia-Ju Bai
2022-02-08 17:22 ` Karsten Graul
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=11fe65b8-eda4-121e-ec32-378b918d0909@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).