summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2015-01-28 11:58:39 -0600
committerGregory Nutt <gnutt@nuttx.org>2015-01-28 11:58:39 -0600
commitf9eb4dfba09aa193f604e17d1ac569c23af0578f (patch)
treec0c04f9440e8b97f4352b7c9ad3685dac82a4951
parenta192f2d2158c7e4d18e2eeabc84f24af82eeb096 (diff)
downloadnuttx-f9eb4dfba09aa193f604e17d1ac569c23af0578f.tar.gz
nuttx-f9eb4dfba09aa193f604e17d1ac569c23af0578f.tar.bz2
nuttx-f9eb4dfba09aa193f604e17d1ac569c23af0578f.zip
Update ChangeLog
-rwxr-xr-xnuttx/ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/nuttx/ChangeLog b/nuttx/ChangeLog
index d1e6eea6b..64681f1e7 100755
--- a/nuttx/ChangeLog
+++ b/nuttx/ChangeLog
@@ -9547,3 +9547,9 @@
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).
+ * net/tcp/tcp_send_buffered.c and tcp_wrbuffer.c: Fix another deadlock
+ condition. tcp_write_buffer_alloc() calls sem_wait() with network
+ locked. That worked if CONFIG_NET_NOINTS was not defined because
+ interrupts are automatically restored when the wait happens. But
+ with CONFIG_NET_NOINTS=y, the wait blocks with the network locked --
+ bad style and also can lead to a deadlock condition (2015-01-28).