Re: [PATCH 2.6.19-git19] BUG due to bad argument to ieee80211softmac_assoc_work
Hello Uli, Yes, apologies, I had been waiting for an abandoned bugzilla entry to get attention, and when I realized it was assigned to a dead-end, I had simply posted the patch without checking for prior messages. I was further confused by the fact that it hadn't made its way into any of the 19-gitX sets (and for that matter, the window for 2.6.20-rc1 has come and gone and this still remains unfixed), despite how clear the error was and how trivial the fix seems. -Mike On 12/14/06, Uli Kunitz <[EMAIL PROTECTED]> wrote: Michael, I sent a patch to this list on Sunday, that patched the problem. It seems to be migrated into the wireless-2.6 git tree. Regards, Uli Am 13.12.2006 um 19:17 schrieb Michael Bommarito: > This didn't get much attention on bugzilla and I figured it was > important enough to forward along to the whole list since it's been > lingering around in ieee80211-softmac since 19-git5 at least. > http://bugzilla.kernel.org/show_bug.cgi?id=7657 > > Somebody was passing the whole mac device structure to > ieee80211softmac_assoc_work instead of just the assocation work, which > lead to much death and locking. > > Attached is a patch that fixes this (the actual change is two lines > but context provided in patch for review). The dmesg containing call > trace is attached to the bugzilla entry above. > > -Mike > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Uli Kunitz - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2.6.19-git19] BUG due to bad argument to ieee80211softmac_assoc_work
Ah, apologies, it's exam time and I probably didn't look hard enough
on the mailing list before posting. For the record though, I'd posted
the bug (no patch) to bugzilla on the 9th (although it looks as if the
email address it was assigned to is actually defunct - anyone know why
bugzilla is still using [EMAIL PROTECTED] ?)
Anyway, again, sorry for the duplicate!
-Mike
On 12/14/06, Ray Lee <[EMAIL PROTECTED]> wrote:
On 12/13/06, Michael Bommarito <[EMAIL PROTECTED]> wrote:
> Sorry, realized I might not have been clear as to what I meant! The
> patch was attached to the bugzilla entry, but I'll attach it here as
> well. My description of the patch itself was really as complicated as
> it gets too (just two lines, switch (void*)mac to
> &mac->assoc.work.work in
> net/ieee80211/softmac/ieee80211softmac_assoc.c), just a small bug
> while somebody was rushing through the work/delayed_work changes.
--- net/ieee80211/softmac/ieee80211softmac_assoc.c 2006-12-13
11:23:03.0 -0500
+++ net/ieee80211/softmac/ieee80211softmac_assoc.c 2006-12-13
11:24:26.0 -0500
@@ -167,7 +167,7 @@
ieee80211softmac_assoc_notify_scan(struct net_device *dev, int
event_type, void *context)
{
struct ieee80211softmac_device *mac = ieee80211_priv(dev);
- ieee80211softmac_assoc_work((void*)mac);
+ ieee80211softmac_assoc_work(&mac->associnfo.work.work);
}
static void
@@ -177,7 +177,7 @@
switch (event_type) {
case IEEE80211SOFTMAC_EVENT_AUTHENTICATED:
- ieee80211softmac_assoc_work((void*)mac);
+ ieee80211softmac_assoc_work(&mac->associnfo.work.work);
break;
case IEEE80211SOFTMAC_EVENT_AUTH_FAILED:
case IEEE80211SOFTMAC_EVENT_AUTH_TIMEOUT:
Good catch, though it was already caught. See:
http://lkml.org/lkml/2006/12/12/46
...for (basically) the same patch.
But again, good catch :-).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2.6.19-git19] BUG due to bad argument to ieee80211softmac_assoc_work
Sorry, realized I might not have been clear as to what I meant! The patch was attached to the bugzilla entry, but I'll attach it here as well. My description of the patch itself was really as complicated as it gets too (just two lines, switch (void*)mac to &mac->assoc.work.work in net/ieee80211/softmac/ieee80211softmac_assoc.c), just a small bug while somebody was rushing through the work/delayed_work changes. -Mike On 12/13/06, Mike Galbraith <[EMAIL PROTECTED]> wrote: On Wed, 2006-12-13 at 13:17 -0500, Michael Bommarito wrote: > This didn't get much attention on bugzilla and I figured it was > important enough to forward along to the whole list since it's been > lingering around in ieee80211-softmac since 19-git5 at least. > http://bugzilla.kernel.org/show_bug.cgi?id=7657 > > Somebody was passing the whole mac device structure to > ieee80211softmac_assoc_work instead of just the assocation work, which > lead to much death and locking. > > Attached is a patch that fixes this (the actual change is two lines > but context provided in patch for review). The dmesg containing call > trace is attached to the bugzilla entry above. -ENOPATCH :) patch-ieee80211softmac_assoc_work Description: Binary data
[PATCH 2.6.19-git19] BUG due to bad argument to ieee80211softmac_assoc_work
This didn't get much attention on bugzilla and I figured it was important enough to forward along to the whole list since it's been lingering around in ieee80211-softmac since 19-git5 at least. http://bugzilla.kernel.org/show_bug.cgi?id=7657 Somebody was passing the whole mac device structure to ieee80211softmac_assoc_work instead of just the assocation work, which lead to much death and locking. Attached is a patch that fixes this (the actual change is two lines but context provided in patch for review). The dmesg containing call trace is attached to the bugzilla entry above. -Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
