From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Bob Copeland <bcopeland@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Pavel Roskin <proski@gnu.org>
Subject: Re: [ath5k-devel] BUG in freq_reg_info_regd
Date: Fri, 17 Apr 2009 11:22:17 +0100 [thread overview]
Message-ID: <49E85859.5060603@tuffmail.co.uk> (raw)
In-Reply-To: <b6c5339f0904150908nb23cf89n9f36bba5a29f955e@mail.gmail.com>
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
prev parent reply other threads:[~2009-04-17 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 10:45 net/wireless/reg.c:1196: warning: ‘channel_after’ may be used uninitialised in this function Alan Jenkins
2009-04-15 10:58 ` Alan Jenkins
2009-04-15 13:02 ` John W. Linville
2009-04-15 14:17 ` BUG in freq_reg_info_regd Alan Jenkins
2009-04-15 15:09 ` [ath5k-devel] " Bob Copeland
2009-04-15 15:13 ` Alan Jenkins
2009-04-15 16:08 ` Bob Copeland
2009-04-17 10:22 ` Alan Jenkins [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=49E85859.5060603@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=bcopeland@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.