[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #44032] select might work on invalid/reused socket
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #44032] select might work on invalid/reused socket |
Date: |
Sat, 17 Jan 2015 20:18:09 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36 |
URL:
<http://savannah.nongnu.org/bugs/?44032>
Summary: select might work on invalid/reused socket
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: Sa 17 Jan 2015 20:18:08 GMT
Category: sockets/netconn
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release:
lwIP version: git head
_______________________________________________________
Details:
When a socket gets closed and reused from another thread while select is
waiting on it, 'select_waiting--' can be executed on this socket although it's
not the socket where 'select_waiting++' was executed before (this mainly
depends on the priorities of the threads using sockets).
To circumvent this, we could either not completely free sockets where select
is waiting or add a global 'sockalloc' counter, stored per socket, which
select could used to detect newly allocated sockets.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?44032>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-devel] [bug #44032] select might work on invalid/reused socket,
Simon Goldschmidt <=