After reading the rest of the thread, there seems to be a newer (somewhat cleaner?) patch. [1, attached].

[1] http://www.spinics.net/lists/linux-wireless/msg51493.html

Created attachment 461106 [details]
Updated Channel lock patch

Thanks for the report.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

John, is this ok to add ?

I would rather not add it, since there has been no resolution upstream.

What is the use case here?  Is there just a single monitor interface?

Created attachment 520666 [details]
monitor-channel-switch.patch

Are you (reporter) in a position to test a patch?  Compile tested only.

*** Bug 647800 has been marked as a duplicate of this bug. ***

I no longer have an F14 machine to test it on.
Would F15 do?

- Gilboa

Sure -- the patch might even apply there. :-)  If you can't make it apply, let me know and I'll take another swipe at it...

OK. Thanks. Working on it.

- Gilboa

I've rebuilt only the mac80211 module using a local Makefile; thus far it seems to work just fine.

- Gilboa

So says Johannes Berg <johannes>:

> @@ -131,5 +153,8 @@ int cfg80211_set_freq(struct cfg80211_registered_device
>       if (wdev)
>               wdev->channel = chan;
>
> +     if (mon_wdev)
> +             mon_wdev->channel = chan;

This is the issue, it doesn't work. I'm finally getting to a point where
I'm not sure I care any more though, if the people who user monitor mode
are happy with this patch and don't care about getting the wrong results
then who am I to complain?

Maybe you should respin this patch with just the last bit. The checking
above is pretty much useless. Also please add *huge* warnings to it that
this *will* give the wrong results.

Alternatively, it could be fixed up properly, but I think to do that we
need a cfg80211 get_channel op to ask mac80211 what channel it really is
using. Not that this will help much once we go multi-channel :-)

Most likely I don't fully understand the internal complexities of the different driver/802.11/etc layers (hence I don't really understand the problem with the second part of the patch) - but at least in my use case I only monitor a single pre-selected AP with a fixed channel, so the patch works wonders.

- Gilboa

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping