From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: jerome.pouiller@silabs.com, Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [BUG] staging: wfx: possible deadlock in wfx_conf_tx() and wfx_add_interface()
Date: Tue, 1 Feb 2022 15:09:34 +0800 [thread overview]
Message-ID: <6f489bf2-bac0-8030-7ea5-6f5c12daa568@gmail.com> (raw)
Hello,
My static analysis tool reports a possible deadlock in the wfx driver in
Linux 5.16:
wfx_conf_tx()
mutex_lock(&wdev->conf_mutex); --> Line 225 (Lock A)
wfx_update_pm()
wait_for_completion_timeout(&wvif->set_pm_mode_complete, ...); -->
Line 3019 (Wait X)
wfx_add_interface()
mutex_lock(&wdev->conf_mutex); --> Line 737 (Lock A)
complete(&wvif->set_pm_mode_complete); --> Line 758 (Wake X)
When wfx_conf_tx() is executed, "Wait X" is performed by holding "Lock
A". If wfx_add_interface() is executed at this time, "Wake X" cannot be
performed to wake up "Wait X" in wfx_conf_tx(), because "Lock A" has
been already hold by wfx_conf_tx(), causing a possible deadlock.
I find that "Wait X" is performed with a timeout, to relieve the
possible deadlock; but I think this timeout can cause inefficient execution.
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:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 7:09 Jia-Ju Bai [this message]
[not found] ` <20220201113303.3883-1-hdanton@sina.com>
2022-02-01 11:56 ` [BUG] staging: wfx: possible deadlock in wfx_conf_tx() and wfx_add_interface() Jérôme Pouiller
2022-02-05 8:34 ` Jia-Ju Bai
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=6f489bf2-bac0-8030-7ea5-6f5c12daa568@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jerome.pouiller@silabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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