From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Bob Copeland <me@bobcopeland.com>, Pavel Roskin <proski@gnu.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [BUG] Crda oopses the system
Date: Sun, 31 May 2009 15:47:11 +0300 [thread overview]
Message-ID: <1243774031.5741.5.camel@maxim-laptop> (raw)
In-Reply-To: <20090531062217.GB23972@bombadil.infradead.org>
On Sun, 2009-05-31 at 02:22 -0400, Luis R. Rodriguez wrote:
> On Fri, May 22, 2009 at 01:08:22PM +0300, Maxim Levitsky wrote:
> > I am talking about
> >
> > BUG_ON(!country_ie_regdomain);
> > in net/wireless/reg.c
>
> Please try this patch and leave a window open with this running:
>
> iw event
>
> Please be sure to grab iw from git, not sure if the reg events
> have all gone into an official release yet. What I'm looking for
> is whether or not a previous 11d setting was already processed
> or if the !country_ie_regdomain condition happens from the first
> 11d processing.
>
> Luis
>
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index f87ac1d..1b60dfc 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -2171,7 +2171,11 @@ static int __set_regdom(const struct ieee80211_regdomain *rd)
> * the country IE rd with what CRDA believes that country should have
> */
>
> - BUG_ON(!country_ie_regdomain);
> + if (WARN_ON(!country_ie_regdomain)) {
> + kfree(rd);
> + rd = NULL;
> + return -EINVAL;
> + }
> BUG_ON(rd == country_ie_regdomain);
>
> /*
> @@ -2268,6 +2272,8 @@ int regulatory_init(void)
> if (IS_ERR(reg_pdev))
> return PTR_ERR(reg_pdev);
>
> + country_ie_regdomain = NULL;
> +
> spin_lock_init(®_requests_lock);
> spin_lock_init(®_pending_beacons_lock);
>
I'll test this today.
I have iw from git.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-05-31 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 5:04 [BUG] Crda oopses the system Maxim Levitsky
2009-05-05 18:46 ` Luis R. Rodriguez
2009-05-06 10:47 ` Maxim Levitsky
2009-05-06 20:34 ` Pavel Roskin
2009-05-10 12:20 ` Maxim Levitsky
2009-05-10 18:33 ` Luis R. Rodriguez
2009-05-10 19:34 ` Maxim Levitsky
2009-05-10 19:36 ` Luis R. Rodriguez
2009-05-12 15:05 ` Maxim Levitsky
2009-05-12 17:24 ` Luis R. Rodriguez
2009-05-12 17:34 ` Maxim Levitsky
2009-05-12 22:00 ` Luis R. Rodriguez
2009-05-12 22:07 ` Maxim Levitsky
2009-05-13 21:28 ` Luis R. Rodriguez
2009-05-13 23:08 ` Maxim Levitsky
2009-05-13 23:12 ` Luis R. Rodriguez
2009-05-13 23:22 ` Maxim Levitsky
2009-05-13 23:28 ` Luis R. Rodriguez
2009-05-13 23:47 ` Maxim Levitsky
2009-05-14 0:07 ` Luis R. Rodriguez
2009-05-14 14:20 ` Bob Copeland
2009-05-19 14:17 ` Maxim Levitsky
2009-05-22 0:20 ` Maxim Levitsky
2009-05-22 0:36 ` Luis R. Rodriguez
2009-05-22 10:08 ` Maxim Levitsky
2009-05-31 6:22 ` Luis R. Rodriguez
2009-05-31 12:47 ` Maxim Levitsky [this message]
2009-05-31 20:54 ` Maxim Levitsky
2009-05-31 21:13 ` Maxim Levitsky
2009-05-31 22:24 ` Luis R. Rodriguez
2009-05-31 22:48 ` Maxim Levitsky
2009-06-01 0:32 ` Bob Copeland
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=1243774031.5741.5.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@bombadil.infradead.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--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 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).