[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #35541] PPP Memory Leak
From: |
Woody Wu |
Subject: |
[lwip-devel] [bug #35541] PPP Memory Leak |
Date: |
Thu, 16 Feb 2012 03:17:04 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.122 Safari/534.30 |
URL:
<http://savannah.nongnu.org/bugs/?35541>
Summary: PPP Memory Leak
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: narke
Submitted on: Thu 16 Feb 2012 03:17:03 AM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release:
lwIP version: 1.4.0
_______________________________________________________
Details:
I found the bug in practice. Before I call pppSigHUP, there might be
some un-concluded frame accumulated in ppp, thus a pbuf might be
allocated but not yet freed. This un-concluded frame might be an
incorrect PPP frame. After I call the pppSigHUP, the allocated pbuf
stay in ppp as allocated state. The detail you can refer to the
pppInProc() function. Then next time, when I have to reopen the ppp,
I can only call the pppOverSerialOpen() function, but this function
will reset ppp receive parser state variables, that results in the
allocated pbuf will never get chance to be freed.
Currently, my workaround solution is to feed the ppp with a 0x7e character
before I can pppSigHUP. This extra ppp ending flag cause the pppInProc()
state machine check the un-concluded frame and release it.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?35541>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #35541] PPP Memory Leak,
Woody Wu <=