Gregory Nutt c4bd6f52b5 Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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 verisons of the same interfaces (like iob_tryalloc()).  The TCP read-ahead logic now uses only these non-waiting interfaces.

2015-01-27 21:23:42 -06:00

..

iob_add_queue.c

Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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.

2015-01-27 21:23:42 -06:00

iob_alloc_qentry.c

Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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.

2015-01-27 21:23:42 -06:00

iob_alloc.c

Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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.

2015-01-27 21:23:42 -06:00

iob_clone.c

…

iob_concat.c

…

iob_contig.c

…

iob_copyin.c

Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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.

2015-01-27 21:23:42 -06:00

iob_copyout.c

…

iob_dump.c

Update everything under nuttx/net to use the corrected syslog interfaces

2014-10-08 10:48:11 -06:00

iob_free_chain.c

…

iob_free_qentry.c

…

iob_free_queue.c

…

iob_free.c

…

iob_initialize.c

…

iob_pack.c

…

iob_peek_queue.c

…

iob_remove_queue.c

…

iob_test.c

…

iob_trimhead_queue.c

…

iob_trimhead.c

IOB: Change suggested by Rony Xln

2014-07-08 07:13:50 -06:00

iob_trimtail.c

More fixes to problems noted by cppcheck. Some are kind of risky; some are real bugs.

2014-11-25 14:10:35 -06:00

iob.h

Networking: The are issues with the TCP write-ahead buffering if CONFIG_NET_NOINTS is 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.

2015-01-27 21:23:42 -06:00

Kconfig

…

Make.defs

…