From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Mark Asselstine <mark.asselstine@windriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac and WIPHY_FLAG_NETNS_OK
Date: Tue, 14 Mar 2017 12:28:26 +0100 [thread overview]
Message-ID: <1489490906.28373.3.camel@sipsolutions.net> (raw)
In-Reply-To: <df16691e-62f7-4c95-0534-48d1dea4f5ba@broadcom.com> (sfid-20170314_105145_213435_11AD40CE)
> It never came up with any projects so far. I doubt that the patch
> below is sufficient. I suspect something more is needed. Using git
> blame I ended up finding these commits:
>
> a272a72 mac80211: allow using network namespaces
This is needed in brcm drivers.
> 463d018 cfg80211: make aware of net namespaces
This has no impact on brcm drivers :)
> 5061b0c mac80211: cooperate more with network namespaces
This shouldn't be needed, you're not referring to init_net in brcm
drivers.
> I think what is required from brcmfmac is to set netns for each
> netdev that we create to the same netns as the wiphy instance using
> wiphy_net().
Yes, like the mac80211 patch above.
> Not sure if there is more to consider, but hopefully Johannes can
> comment on this although the mentioned commits have been around for a
> while.
I don't think there's anything else.
> > wiphy->flags |= WIPHY_FLAG_PS_ON_BY_DEFAULT |
> > WIPHY_FLAG_OFFCHAN_TX |
> > - WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL;
> > + WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL |
> > + WIPHY_FLAG_NETNS_OK;
This is not sufficient, you still have to set the netns for newly
created netdevs.
johannes
next prev parent reply other threads:[~2017-03-14 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2253234.njokx7NVYT@yow-masselst-lx1>
2017-03-14 9:51 ` brcmfmac and WIPHY_FLAG_NETNS_OK Arend Van Spriel
2017-03-14 11:28 ` Johannes Berg [this message]
2017-03-14 12:41 ` Arend Van Spriel
2017-03-14 13:21 ` Mark Asselstine
2017-03-14 13:27 ` Arend Van Spriel
2017-03-14 13:37 ` Mark Asselstine
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=1489490906.28373.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mark.asselstine@windriver.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;
as well as URLs for NNTP newsgroup(s).