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: [PATCH] cfg80211: fix set_monitor_enabled
Date: Thu, 12 Jul 2012 19:07:13 +0200 [thread overview]
Message-ID: <1342112833.4531.44.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEfP6qUfrnxeCHoJ_XrD4H_HjkVw685C04XCrVm=1wD8Mw@mail.gmail.com> (sfid-20120712_183750_406882_C65E8DAC)
On Thu, 2012-07-12 at 19:37 +0300, Eliad Peller wrote:
> On Thu, Jul 12, 2012 at 7:31 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2012-07-12 at 19:26 +0300, Eliad Peller wrote:
> >
> >> >> why not always do it only on IFACE_UP?
> >> >
> >> > Yeah .. thought so too at first, but it doesn't work, say you have this
> >> > situation:
> >> >
> >> > * up moni0 (monitor)
> >> > * up wlan0 (managed)
> >> >
> >> > Then the set_monitor_enabled(false) should happen before wlan0 is
> >> > brought up, otherwise mac80211/the driver will correctly reject wlan0
> >> > being brought up.
> >> >
> >> but you don't call set_monitor_enabled(false) on pre_up in your
> >> patch...
> >
> > It does, this is what happens when wlan0 is brought up:
> >
>
> >> if (monitors_only) {
> >
> > no, we'll go into else
> >
> i completely overlooked this if :)
>
> >> afaict, the only effect of pre_up is updating
> >> rdev->num_running_ifaces/rdev->num_running_monitor_ifaces, which don't
> >> seem to matter much...
> >
> > No :-)
> >
> thanks for the detailed walkthrough :D
:-)
However, I just realised that it's still all broken. We must not do any
accounting in NETDEV_PRE_UP, because it might fail afterwards and we'd
never get NETDEV_UP, but also don't get NETDEV_DOWN or anything else.
It seems we can't fix it and will have to revert the monitor interface
tracking changes in cfg80211/mac80211.
johannes
prev parent reply other threads:[~2012-07-12 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 15:15 [PATCH] cfg80211: fix set_monitor_enabled Johannes Berg
2012-07-12 16:00 ` Eliad Peller
2012-07-12 16:03 ` Johannes Berg
2012-07-12 16:26 ` Eliad Peller
2012-07-12 16:31 ` Johannes Berg
2012-07-12 16:37 ` Eliad Peller
2012-07-12 17:07 ` Johannes Berg [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=1342112833.4531.44.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).