Re: [lwip-devel] Sockets: select_waiting overflow

[Joan Lledó]

Hi Simon,

It's not a different bug, I was explaining to Stian the problem I have
in my port, that leads to create hundreds of threads waiting in
lwip_select().

In particular, in my system, three threads are created for any
character the SSH server sends or receives, that is, hundreds of
threads may be created in a few seconds. Since lwip_select is called
with no timeout, these threads get locked and never return. Then, the
next event creates another three threads, and so on, until
select_waiting
overflows.


2017-07-06 20:41 GMT+02:00 address@hidden <address@hidden>:
> Joan Lledó wrote:
>>>
>>> Hundreds of threads will cause the byte-overflow mentioned by Simon.
>>>
>>> So, in your example you have three threads, each thread has a different
>>> file-descriptor they are responsible for, which they set in their own
>>> fd_set
>>> and call select().
>>
>> Yes, exactly.
>
>
> Wait a minute, I thought this was about select_waiting overflow. With three
> threads, how can this overflow? Sounds like a different bug?
>
> Simon
>
>
> _______________________________________________
> lwip-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lwip-devel