[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #19162] lwip_sendto: possible to corrupt remote addr/p
[lwip-devel] [bug #19162] lwip_sendto: possible to corrupt remote addr/port connection state
Tue, 27 Feb 2007 08:53:31 +0000
Opera/8.02 (X11; Linux i686; U; en)
Update of bug #19162 (project lwip):
Severity: 3 - Normal => 1 - Wish
Item Group: Faulty Behaviour => Change Request
Follow-up Comment #1:
You're right about the assumption that there's only one calling thread per
netconn. That is a deliberate decision to keep things simple, and in most
cases will be true. If a resource of any sort is used from two or more
threads, it is usually up to the threads to synchronize access to it, and in
this respect a netconn is no different.
It does differ to what people might expect though, so perhaps we need to
document this aspect of the API better.
An alternative would be to overhaul the sockets API as you suggest and make
it thread safe. I think that is unlikely to happen, but leave the option
open for others if they wish to do this.
Reply to this item at:
Message sent via/by Savannah