diff options
| author | nbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73> | 2007-07-23 00:37:35 +0000 |
|---|---|---|
| committer | nbd <nbd@3c298f89-4303-0410-b956-a3cf2f4a3e73> | 2007-07-23 00:37:35 +0000 |
| commit | dc872da1d7f4157a58ba07f812e81a2c9f67c40e (patch) | |
| tree | a866414e2cb1efdcef108573db4ce8a4576a0ed7 | |
| parent | efde7ff8e6584d5bcf47cd567904411526b7e404 (diff) | |
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)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@8111 3c298f89-4303-0410-b956-a3cf2f4a3e73
| -rw-r--r-- | package/madwifi/patches/128-adhoc_memleak.patch | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/package/madwifi/patches/128-adhoc_memleak.patch b/package/madwifi/patches/128-adhoc_memleak.patch new file mode 100644 index 0000000000..75c2261429 --- /dev/null +++ b/package/madwifi/patches/128-adhoc_memleak.patch @@ -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 { |