lwIP - A Lightweight TCP/IP stack - Bugs: bug #26027, Chaining netbufs
You are not allowed to post comments on this tracker with your current authentication level.
bug #26027: Chaining netbufs
| Submitter: | Hans-Erik Floryd <hefloryd> | ||
| Submitted: | Fri 27 Mar 2009 01:48:56 PM UTC | ||
| Category: | None | Severity: | 3 - Normal |
| Item Group: | Faulty Behaviour | Status: | Fixed |
| Privacy: | Public | Assigned to: | goldsimon |
| Open/Closed: | Closed | Planned Release: | None |
| lwIP version: | 1.3.0 | ||
|
Wed 15 Apr 2009 02:57:51 PM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
|
Fri 27 Mar 2009 01:48:56 PM UTC, original submission:
When trying to chain two netbufs (identifier and payload) together, netbuf_chain calls memp_free on the tail. It is unclear if/how the pbuf associated with the tail can then be reclaimed. Test case:
|
Hans-Erik Floryd <hefloryd> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

I just wondered who can ever have uses netbuf_chain without a big memory leak?
I've changed it to calling pbuf_cat instead of pbuf_chain so that the second netbuf must not be referenced/freed after passing it to netbuf_chain.