Search Linux Wireless

Re: [ath5k-devel] BUG in freq_reg_info_regd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bob Copeland wrote:
>>> Hmm, null pointer is probably custom_regd since reg_rule comes from
>>> the stack and wiphy should've been validated a lot earlier.
>>>
>>> Mind posting the objdump -S net/wireless/reg.o ?
>>>
>>>       
>> Sure.  It's 120k so I trimmed the CC list.
>>     
>
> Darn, no debug info..  In hindsight I should've just asked for
> the scripts/markup_oops.pl treatment :)
>
> Ok, I was wrong: it's last_request.  This looks very similar to the bug you
> had a few days ago to which Pavel Roskin responded.  I don't think anything
> changed wrt last_request initialization, so maybe some kind of module
> loading race again?
>   

Could be.  It goes away if I just make cfg80211 built-in (and leave
mac80211 and ath/ath5k as modules).

Note that unlike the previous bug, this only happens with
wireless-testing.  It's still present in today's wireless-testing,
v2.6.30-rc2-21665-gca0be26.  I haven't seen it while testing mainline.

Thanks
Alan

--
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

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux