From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Thomas Tuttle <linux-kernel@ttuttle.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Oops with 2.6.24 git when loading iwl3945
Date: Mon, 3 Dec 2007 22:19:41 +0300 [thread overview]
Message-ID: <20071203191941.GB7328@cvg> (raw)
In-Reply-To: <1196617561.16481.1224371239@webmail.messagingengine.com>
[Thomas Tuttle - Sun, Dec 02, 2007 at 12:46:01PM -0500]
| On Sun, 2 Dec 2007 19:43:16 +0300, "Cyrill Gorcunov"
| <gorcunov@gmail.com> said:
| > [Thomas Tuttle - Tue, Nov 27, 2007 at 03:43:57PM -0500]
| > | Hey.
| > |
| > | I'm using a git snapshot that gentoo distributed mere hours ago (so I'm
| > | fairly confident it's current), and I'm getting an Oops when I try to
| > | load the iwl3945 driver. I've attached it as plain text.
| > |
| > | Hope this helps,
| > |
| > | Thomas Tuttle
| >
| > Hi Thomas,
| > Could you please test the patch?
|
| It didn't help. The original oops says the problem was in strcmp. It
| was a GPF, which suggests to me that one of the arguments is NULL.
| Since ops->name is checked at the beginning of the function, the only
| other possibility is that alg->ops->name is NULL. I added a bit of code
| to check for this, and it turns out that one of the strings was indeed
| NULL. I didn't know where to go from there in debugging, but I hope it
| helps.
|
| Thanks,
|
| Thomas Tuttle
|
Hi Thomas,
could you please try that one ;)
Ayway as my previous patch and this one have to be applied anyway (regardless
the OOPs you catched). So I've sent previous patch to list and this one too,
but that is more important for - does these (both) patch helped. Thanks a lot
for patience (i know the problem is in strcmp but it seems that is a side issue -
main problems seems to be in sych. events)
Cyrill
---
From: Cyrill Gorcunov <gorcunov@gmail.com>
Date: Mon, 3 Dec 2007 22:12:30 +0300
Subject: [PATCH] [PATCH] NET: mac80211 - fix inappropriate memory freeing
This patch does fix inappropriate memory freeing in case
of requested rate_control_ops was not found. In this case
the list head entity is going to be accidently wasted.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
---
net/mac80211/ieee80211_rate.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/mac80211/ieee80211_rate.c b/net/mac80211/ieee80211_rate.c
index 3260a4a..c3f2783 100644
--- a/net/mac80211/ieee80211_rate.c
+++ b/net/mac80211/ieee80211_rate.c
@@ -60,11 +60,11 @@ void ieee80211_rate_control_unregister(struct rate_control_ops *ops)
list_for_each_entry(alg, &rate_ctrl_algs, list) {
if (alg->ops == ops) {
list_del(&alg->list);
+ kfree(alg);
break;
}
}
mutex_unlock(&rate_ctrl_mutex);
- kfree(alg);
}
EXPORT_SYMBOL(ieee80211_rate_control_unregister);
--
1.5.3.5
prev parent reply other threads:[~2007-12-03 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 20:43 Oops with 2.6.24 git when loading iwl3945 Thomas Tuttle
2007-11-28 5:48 ` Andrew Morton
2007-11-28 21:43 ` Jeremy Fitzhardinge
2007-11-28 23:50 ` Rafael J. Wysocki
2007-12-02 16:43 ` Cyrill Gorcunov
2007-12-02 17:46 ` Thomas Tuttle
2007-12-02 18:05 ` Cyrill Gorcunov
2007-12-03 5:25 ` Cyrill Gorcunov
2007-12-03 19:19 ` Cyrill Gorcunov [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=20071203191941.GB7328@cvg \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@ttuttle.net \
--cc=linux-kernel@vger.kernel.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