On Mon, Sep 8, 2008 at 6:16 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote:
> On Mon, 2008-09-08 at 17:05 +0200, Johannes Berg wrote:
>
>> > Can you explain why? Or can anybody else explain why we do this
>> > difference at all? And how should mesh behave?
>>
>> Actually, I do understand the difference now (explanation added below)
>> and if I'm guessing the problem you're having correctly your patch is
>> wrong. I think you want something like the patch below (never mind the
>> fact that it's against scan.c, I'm shuffling code)
>
>> if (local->sta_sw_scanning || local->sta_hw_scanning) {
>> if (local->scan_sdata == sdata)
>> return 0;
>> return -EBUSY;
>> }
>
> Then again, ieee80211_sta_start_scan does that check as well, so now I'm
> confused.
The bug is that scan can be triggered in STA and IBSS internally. If
you request scan from the application (iwlist) while
internally scan is running application won't fetch scan results
because the -EBUSY is returned on scan request.
Tomas
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
