[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes
From: |
David van Moolenbroek |
Subject: |
[lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes |
Date: |
Thu, 12 Jan 2017 21:00:48 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 |
Follow-up Comment #4, bug #50040 (project lwip):
Hmm, fair enough.. so just to update my own view on this bug then.. mem_size_t
is 16-bit on 1) pool-based configs and 2) memory-constrained heap-based
configs. If in the case of #1 such large allocations (e.g. the udp_input case)
themselves are considered the real problem (see my lwip-devel reply regarding
a way forward there, assuming the mail gets through), and #2 is not expected
to handle full-sized packets, then the mem_size_t definition is fine as it is
and all that is needed is an extra overflow 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, 2017/01/12
- [lwip-devel] [bug #50040] pbuf_alloc(..., 65534, PBUF_RAM) succedes,
David van Moolenbroek <=
- [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