buglwIP - A Lightweight TCP/IP stack - Bugs: bug #34584, Deadlock on multithread enviroment

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #34584: Deadlock on multithread enviroment

Submitter:  Boberek <bober>
Submitted:  Tue 18 Oct 2011 07:36:17 AM UTC
   
 
Category:  sockets/netconn Severity:  3 - Normal
Item Group:  Crash Error Status:  Invalid
Privacy:  Public Assigned to:  goldsimon
Open/Closed:  Closed Planned Release:  None
lwIP version:  CVS Head

Tue 18 Oct 2011 08:22:45 AM UTC, comment #1: 

You could call it a bug, but currently, we do not support using a socket from multiple threads at once (e.g. read/write or read/close).

-> closing as invalid

Simon Goldschmidt <goldsimon>
Group administrator
Tue 18 Oct 2011 07:36:17 AM UTC, original submission:  

I am working on multithread environment.
I use Tcp socket.
One thread after accept calls read() on socket,
Second thread wants to close this socket. Call shutdown() or close().
Function close(), shutdown() free mbox.
But after close, reading thread  still wait on mbox !.

My question: It is bug ? or LwIp socket functions witch use the same socket be used from different thread.

Boberek <bober>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by goldsimon (Posted a comment)
  • -email is unavailable- added by bober (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-10-18 goldsimon StatusNone Invalid
        Assigned toNone goldsimon
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code