From: duoming@zju.edu.cn
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
paskripkin@gmail.com, martin@kaiser.cx, straube.linux@gmail.com,
kuba@kernel.org
Subject: Re: [PATCH] drivers: staging: r8188eu: Fix sleep-in-atomic-context bug in rtw_join_timeout_handler
Date: Fri, 21 Oct 2022 14:32:12 +0800 (GMT+08:00) [thread overview]
Message-ID: <77ff753.140ebd.183f93dfb04.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <Y1FtZzV9wRQRaTYk@kroah.com>
Hello,
On Thu, 20 Oct 2022 17:46:47 +0200 Greg KH wrote:
> On Tue, Oct 18, 2022 at 04:34:24PM +0800, Duoming Zhou wrote:
> > The rtw_join_timeout_handler() is a timer handler that
> > runs in atomic context, but it could call msleep().
> > As a result, the sleep-in-atomic-context bug will happen.
> > The process is shown below:
> >
> > (atomic context)
> > rtw_join_timeout_handler
>
> Wait, how is this an atomic timeout?
Because this function is defined as a timer handler of "assoc_timer".
The following is the detail:
void rtw_init_mlme_timer(struct adapter *padapter)
{
struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
timer_setup(&pmlmepriv->assoc_timer, rtw_join_timeout_handler, 0);
...
}
https://elixir.bootlin.com/linux/latest/source/drivers/staging/r8188eu/os_dep/mlme_linux.c#L36
> When can that happen?
When the adapter trys to join and selects scanning queue successfully,
the assoc_timer will be actived. If this process is timeout, the callback
function rtw_join_timeout_handler will run.
> > _rtw_join_timeout_handler
> > rtw_do_join
> > rtw_select_and_join_from_scanned_queue
> > rtw_indicate_disconnect
> > rtw_lps_ctrl_wk_cmd
> > lps_ctrl_wk_hdl
> > LPS_Leave
> > LPS_RF_ON_check
> > msleep //sleep in atomic context
>
> How was this found?
>
> > Fix by removing msleep() and replacing with mdelay().
>
> Wouldn't people have seen an error already if msleep() was really called
> in atomic context?
I am sorry, This is the false alarm.
rtw_indicate_disconnect()
-->rtw_lps_ctrl_wk_cmd(padapter, LPS_CTRL_DISCONNECT, 1);
u8 rtw_lps_ctrl_wk_cmd(struct adapter *padapter, u8 lps_ctrl_type, u8 enqueue)
{
...
if (enqueue) {
...
}else {
lps_ctrl_wk_hdl(padapter, lps_ctrl_type);
}
The enqueue equals to 1 and the lps_ctrl_wk_hdl() will not execute.
I will check carefully and avoid false alarm next time. Thank you for your reply.
Best regards,
Duoming Zhou
prev parent reply other threads:[~2022-10-21 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 8:34 Duoming Zhou
2022-10-20 15:46 ` Greg KH
2022-10-21 6:32 ` duoming [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=77ff753.140ebd.183f93dfb04.Coremail.duoming@zju.edu.cn \
--to=duoming@zju.edu.cn \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin@kaiser.cx \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=straube.linux@gmail.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
all inboxes | Powered by JetHome®