From: Kalle Valo <kvalo@codeaurora.org>
To: Xinming Hu <huxm@marvell.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>,
Dmitry Torokhov <dtor@google.com>, <rajatja@google.com>,
Zhiyuan Yang <yangzy@marvell.com>, Tim Song <songtao@marvell.com>,
Cathy Luo <cluo@marvell.com>, James Cao <jcao@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>,
Ellie Reeves <ellierevves@gmail.com>,
Limin Zhu <liminzhu@marvell.com>, Xinming Hu <huxm@marvell.com>
Subject: Re: mwifiex: cfg80211: do not change virtual interface during scan processing
Date: Thu, 7 Dec 2017 13:31:49 +0000 (UTC) [thread overview]
Message-ID: <20171207133150.382D0608BA@smtp.codeaurora.org> (raw)
In-Reply-To: <1512022954-10129-1-git-send-email-huxm@marvell.com>
Xinming Hu <huxm@marvell.com> wrote:
> From: Limin Zhu <liminzhu@marvell.com>
>
> (1) Change virtual interface operation in cfg80211 process reset and
> reinitilize private data structure.
> (2) Scan result event processed in main process will dereference private
> data structure concurrently, ocassionly crash the kernel.
>
> The cornel case could be trigger by below steps:
> (1) wpa_cli mlan0 scan
> (2) ./hostapd mlan0.conf
>
> Cfg80211 asynchronous scan procedure is not all the time operated
> under rtnl lock, here we add the protect to serialize the cfg80211
> scan and change_virtual interface operation.
>
> Signed-off-by: Limin Zhu <liminzhu@marvell.com>
> Signed-off-by: Xinming Hu <huxm@marvell.com>
Patch applied to wireless-drivers-next.git, thanks.
c61cfe49f0f0 mwifiex: cfg80211: do not change virtual interface during scan processing
--
https://patchwork.kernel.org/patch/10084299/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2017-12-07 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 6:22 [PATCH] mwifiex: cfg80211: do not change virtual interface during scan processing Xinming Hu
2017-12-07 13:31 ` Kalle Valo [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=20171207133150.382D0608BA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=cluo@marvell.com \
--cc=dtor@google.com \
--cc=ellierevves@gmail.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=jcao@marvell.com \
--cc=liminzhu@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rajatja@google.com \
--cc=songtao@marvell.com \
--cc=yangzy@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.