From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: linux-wireless@vger.kernel.org, Michal Kazior <michal.kazior@tieto.com>
Subject: Re: [RFC 1/2] mac80211: add explicit monitor interface if needed
Date: Fri, 30 Mar 2012 08:39:15 +0200 [thread overview]
Message-ID: <1333089555.3908.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEdx6=58pyiEFWAiLGvtJ9eSTacyKD3Y-jKaR-7iDrF3zg@mail.gmail.com> (sfid-20120329_220943_880343_818A1AF7)
On Thu, 2012-03-29 at 22:09 +0200, Eliad Peller wrote:
> > + if (WARN_ON(!sdata))
> > + return;
> > +
> ...
>
> > @@ -280,6 +339,8 @@ static int ieee80211_do_open(struct net_
> > break;
> > default:
> > if (coming_up) {
> > + ieee80211_del_virtual_monitor(local);
> > +
>
> i think this will always trigger the warning?
Yeah, somehow I didn't see this in my first round of testing. I
distinctly remember thinking "I need to remove the warning then" but
clearly never did :-)
> > - if (WARN_ON(sdata->vif.type == NL80211_IFTYPE_AP_VLAN ||
> > - sdata->vif.type == NL80211_IFTYPE_MONITOR))
> > + if (WARN_ON(sdata->vif.type == NL80211_IFTYPE_AP_VLAN))
> > return -EINVAL;
> >
> maybe check for IEEE80211_HW_WANT_MONITOR_VIF instead?
Good point, should do that.
johannes
next prev parent reply other threads:[~2012-03-30 6:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:13 [RFC 0/2] mac80211 queue redesign Johannes Berg
2012-03-28 9:13 ` [RFC 1/2] mac80211: add explicit monitor interface if needed Johannes Berg
2012-03-29 20:09 ` Eliad Peller
2012-03-30 6:39 ` Johannes Berg [this message]
2012-03-28 9:13 ` [RFC 2/2] mac80211: add improved HW queue control Johannes Berg
2012-03-28 9:26 ` Johannes Berg
2012-04-02 9:22 ` [RFC v2] " Johannes Berg
2012-03-28 12:00 ` [RFC 0/2] mac80211 queue redesign Johannes Berg
2012-03-28 12:49 ` Johannes Berg
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=1333089555.3908.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).