Messages in this thread |  | | Date | Sun, 29 Oct 2000 08:11:23 +0100 | From | Andi Kleen <> | Subject | Re: tcp.c::wait_for_tcp_memory() buggy ? |
| |
On Sun, Oct 29, 2000 at 01:28:38AM -0200, Rik van Riel wrote: > Except for doing a test on tcp_memory_free(sk), where we > do NOT hold the lock we're so dutifully clinging to during > the rest of the loop...
And rechecking it later while holding the loop on the next iteration.
Also usually the caller also does a check again and iterates as needed.
> > As I said, I can't put my finger down on what exactly is > wrong, but this code looks subtle enough that, together > with the bugreport I got (on IRC), I have the feeling that > it just _can't_ be right ...
With the right setup of multiple threads writing all the time on a single socket you could probably starve one, making it loop forever here. (it does not try to be fair)
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |