another attempt at fixing the madwifi memleak for good. i'm 95% sure this is the right fix, but it needs to be tested in a real ad-hoc environment... (#2121)
SVN-Revision: 8111
This commit is contained in:
parent
41cce36da6
commit
2d5f735d91
1 changed files with 13 additions and 0 deletions
13
package/madwifi/patches/128-adhoc_memleak.patch
Normal file
13
package/madwifi/patches/128-adhoc_memleak.patch
Normal file
|
@ -0,0 +1,13 @@
|
|||
Index: madwifi-ng-r2568-20070710/net80211/ieee80211_input.c
|
||||
===================================================================
|
||||
--- madwifi-ng-r2568-20070710.orig/net80211/ieee80211_input.c 2007-07-23 01:48:42.282389707 +0200
|
||||
+++ madwifi-ng-r2568-20070710/net80211/ieee80211_input.c 2007-07-23 01:48:44.214499810 +0200
|
||||
@@ -2875,7 +2875,7 @@
|
||||
}
|
||||
if ((vap->iv_opmode == IEEE80211_M_IBSS) &&
|
||||
(scan.capinfo & IEEE80211_CAPINFO_IBSS)) {
|
||||
- if (!IEEE80211_ADDR_EQ(wh->i_addr2, ni->ni_macaddr)) {
|
||||
+ if (ni == vap->iv_bss) {
|
||||
/* Create a new entry in the neighbor table. */
|
||||
ni = ieee80211_add_neighbor(vap, wh, &scan);
|
||||
} else {
|
Loading…
Reference in a new issue