#334: adhoc memory leak
----------------------------------+-----------------------------------------
      Reporter:  kiru             |       Owner:  anonymous                     
      
          Type:  defect           |      Status:  assigned                      
      
      Priority:  critical         |   Milestone:  version 0.9.0 - move to new 
codebase
     Component:  madwifi: driver  |     Version:  trunk                         
      
    Resolution:                   |    Keywords:  adhoc memory leak             
      
Patch_attached:  0                |  
----------------------------------+-----------------------------------------
Changes (by kiru):

  * status:  new => assigned
  * owner:  => anonymous

Comment:

 {{{
 Based on the patch by Georg in http://madwifi.org/ticket/441, I downloaded
 the r1457 version and the patch for avoiding duplicate node problems in
 input.
 }}}

 Verified!

 I try it with r1467. Without the patch it behaviors as formerly.

 {{{
 test1:~# cat /proc/net/madwifi/ath0/associated_sta |wc -l
 3
 test1:~#
 test1:~# wget -O /dev/null ftp://10.5.1.2/100mega.file
 --15:48:31--  ftp://10.5.1.2/100mega.file
            => `/dev/null'
 Connecting to 10.5.1.2:21... connected.
 Logging in as anonymous ... Logged in!
 ==> SYST ... done.    ==> PWD ... done.
 ==> TYPE I ... done.  ==> CWD not needed.
 ==> PASV ... done.    ==> RETR 100mega.file ... done.
 Length: 104,857,600 (unauthoritative)

  6% [====>
 ] 6,400,160      3.82M/s
 test1:~#
 test1:~# cat /proc/net/madwifi/ath0/associated_sta |wc -l
 837
 test1:~#
 }}}

 And with the nodetable patch (thanks Georg):

 {{{
 test1:/lib/modules# iwconfig ath0
 ath0      IEEE 802.11a  ESSID:"madwifi"
           Mode:Ad-Hoc  Frequency:5.32 GHz  Cell: 02:0E:8E:02:7A:63
           Bit Rate=54 Mb/s   Tx-Power:16 dBm   Sensitivity=0/3
           Retry:off   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality=31/94  Signal level=-64 dBm  Noise level=-95 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
 test1:/lib/modules# wget -O /dev/null ftp://10.5.1.2/100mega.file
 --15:56:32--  ftp://10.5.1.2/100mega.file
            => `/dev/null'
 Connecting to 10.5.1.2:21... connected.
 Logging in as anonymous ... Logged in!
 ==> SYST ... done.    ==> PWD ... done.
 ==> TYPE I ... done.  ==> CWD not needed.
 ==> PASV ... done.    ==> RETR 100mega.file ... done.
 Length: 104,857,600 (unauthoritative)

  6% [=====>
 ] 7,202,352      3.44M/s
 test1:/lib/modules#
 test1:/lib/modules# cat /proc/net/madwifi/ath0/associated_sta |wc -l
 3
 test1:/lib/modules#
 }}}

 So I think the nodetable diff (#441) may be merged into trunk, and resolve
 this problem.

 There is a similar problem in ap-sta mode, that I can't test now, but this
 occurs just if the radio connection losts between the nodes, and the
 station reconnects to the ap. I noticed it with station mode. This way the
 previous connection stays in the associated_sta file, and as a new
 duplication goes into the file.

-- 
Ticket URL: <http://madwifi.org/ticket/334>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity

Reply via email to