From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@codeaurora.org>, Sumit Garg <sumit.garg@linaro.org>
Cc: linux-wireless@vger.kernel.org, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, matthias.schoepfer@ithinx.io,
Philipp.Berg@liebherr.com, Michael.Weitner@liebherr.com,
daniel.thompson@linaro.org, loic.poulain@linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix race in ieee80211_register_hw()
Date: Mon, 06 Apr 2020 14:47:43 +0200 [thread overview]
Message-ID: <1e352e2130e19aec5aa5fc42db397ad50bb4ad05.camel@sipsolutions.net> (raw)
In-Reply-To: <87ftdgokao.fsf@tynnyri.adurom.net>
On Mon, 2020-04-06 at 15:44 +0300, Kalle Valo wrote:
>
> > user-space ieee80211_register_hw() RX IRQ
> > +++++++++++++++++++++++++++++++++++++++++++++
> > | | |
> > |<---wlan0---wiphy_register() |
> > |----start wlan0---->| |
> > | |<---IRQ---(RX packet)
> > | Kernel crash |
> > | due to unallocated |
> > | workqueue. |
[snip]
> I have understood that no frames should be received until mac80211 calls
> struct ieee80211_ops::start:
>
> * @start: Called before the first netdevice attached to the hardware
> * is enabled. This should turn on the hardware and must turn on
> * frame reception (for possibly enabled monitor interfaces.)
True, but I think he's saying that you can actually add and configure an
interface as soon as the wiphy is registered?
The "wlan0" is kinda wrong there, should be "phy0" I guess, and then
interface added from iw?
johannes
next prev parent reply other threads:[~2020-04-06 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 12:21 [PATCH] mac80211: fix race in ieee80211_register_hw() Sumit Garg
2020-04-06 12:44 ` Johannes Berg
2020-04-06 13:00 ` Sumit Garg
2020-04-06 12:44 ` Kalle Valo
2020-04-06 12:47 ` Johannes Berg [this message]
2020-04-06 12:52 ` Kalle Valo
2020-04-06 12:53 ` Johannes Berg
2020-04-06 13:04 ` Kalle Valo
2020-04-06 13:07 ` Johannes Berg
2020-04-06 13:21 ` Sumit Garg
2020-04-06 13:27 ` Kalle Valo
2020-04-06 13:55 ` Krishna Chaitanya
2020-04-06 14:01 ` Johannes Berg
2020-04-06 14:25 ` Krishna Chaitanya
2020-04-06 15:06 ` Johannes Berg
2020-04-06 18:08 ` Krishna Chaitanya
2020-04-07 6:42 ` Sumit Garg
2020-04-06 13:06 ` Sumit Garg
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=1e352e2130e19aec5aa5fc42db397ad50bb4ad05.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Michael.Weitner@liebherr.com \
--cc=Philipp.Berg@liebherr.com \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=matthias.schoepfer@ithinx.io \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.garg@linaro.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 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.