[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes |
Date: |
Thu, 12 Jan 2017 19:25:23 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 |
Follow-up Comment #3, bug #50040 (project lwip):
I don't want to justify these bugs, but lwIP was tranditionally meant for
small platforms, some of them not even having 64KByte of memory. In that case,
small structures *do* count, so having mem_size_t being u16_t does make
sense.
The tradition of such small systems (plus the age of lwIP being started in the
early 2000ths) explains why noone has bothered checking for overflow here :-(
Obviously, pbuf_alloc() should check overflow but as David said, there may be
(and are) more places to check...
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?50040>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, chrysn, 2017/01/12
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, David van Moolenbroek, 2017/01/12
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, David van Moolenbroek, 2017/01/12
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes,
Simon Goldschmidt <=
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, David van Moolenbroek, 2017/01/12
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, Dirk Ziegelmeier, 2017/01/15
- Re: [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, address@hidden, 2017/01/12
- Re: [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes, D.C. van Moolenbroek, 2017/01/12