diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2015-01-27 21:30:44 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2015-01-27 21:30:44 -0600 |
| commit | 9e161f81bbddf6998549c98ad36a48794faaa007 (patch) | |
| tree | d975b378f55372628165ec6205d74022c5ae5f7b | |
| parent | f4aca382e288711895e49f1a79e14d1dd1f9159e (diff) | |
| download | nuttx-9e161f81bbddf6998549c98ad36a48794faaa007.tar.gz nuttx-9e161f81bbddf6998549c98ad36a48794faaa007.tar.bz2 nuttx-9e161f81bbddf6998549c98ad36a48794faaa007.zip | |
Update ChangeLog
| -rwxr-xr-x | nuttx/ChangeLog | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog index 11e43c1dd..d1e6eea6b 100755 --- a/nuttx/ChangeLog +++ b/nuttx/ChangeLog @@ -9535,3 +9535,15 @@ * arch/arm/src/stm32/stm32_rtcc.c and Kconfig: Recent changes to stm32_rtcc.c do not compile with STM32L15XX configurations. From Jussi Kivilinna (2015-01-27). + * net/iob, net/tcp/tcp_callback.c, and include/nuttx/net/iob.h: There + were issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS was + enabled: There is a possibility of deadlocks in certain timing conditions. + I have not seen this with the Tiva driver that I have been users but + other people claim to see the issue on other platforms. Certainly it + is a logic error: The network should never wait for TCP read-ahead + buffering space to be available. It should drop the packets + immediately. This was fixed by duplicating most of the IOB interfaces: + The versions that waited are still present (like iob_alloc()), but now + there are non-waiting versions of the same interfaces (like + iob_tryalloc()). The TCP read-ahead logic now uses only these non- + waiting interfaces (2015-01-27). |