[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #23119] After a read with timeout, the socket is unuse
|
From: |
Jonathan Larmour |
|
Subject: |
[lwip-devel] [bug #23119] After a read with timeout, the socket is unuseable |
|
Date: |
Wed, 30 Apr 2008 17:18:25 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20070530 Fedora/1.5.0.12-1.fc5 Firefox/1.5.0.12 |
Follow-up Comment #2, bug #23119 (project lwip):
I don't remember the discussion, so for all I know this is contrary to
anything I may or may not have said before :-), but as described in this bug,
the timeout should not be fatal.
A grep shows that ERR_TIMEOUT is only used for receive timeouts, so should be
safe to treat specially.
If you go with the principle that sockets should not be operated on by more
than one thread at one time, then the only change need be in lwip_recvfrom I
guess.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?23119>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/