lkml.org 
[lkml]   [1998]   [Sep]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux tcp/ip code has trouble with async network I/O notificati on,
I think it's great that in such a short time you have already identified
the relevant section of code to be altered. This could only happen in an
open development environment.

On Thu, 3 Sep 1998, Andrea Arcangeli wrote:

> On Thu, 3 Sep 1998, Theo Van Dinter wrote:
>
> >FYI: I tried your code on linux 2.1.120pre3 -- works fine from any host I try.
> > 2.1.119pre1 fails as you describe.
>
> Yes, even if I have not tried it in practice. Before reading your message
> I just understood that the point was the `sk->data_ready(sk, 0)' in
> tcp_v4_conn_request() because at that time the req->sk was still NULL
> because the connection was not enstablished yet. I was searching where to
> deliver the SIGIO (after the 3 way handshake when the sock is ready to
> cross data) and reading the solution in pre-patch-2.1.120-3 the right
> place is at the end of tcp_v4_syn_recv_sock().
>
> So definetively pre-2.1.120-3 is fixed.
>
> I don' t know which is the state of 2.0.36xxx but sure we have to remove
> the sk->data_ready(sk,0) from tcp_conn_request (and _fake()).
>
> Andrea[s] Arcangeli
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
>
>



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:44    [W:0.030 / U:0.404 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site