Commit in reactos/drivers/lib/oskittcp/oskittcp on MAIN
tcp_output.c+13-51.7 -> 1.8
- Reformulate comment.

reactos/drivers/lib/oskittcp/oskittcp
tcp_output.c 1.7 -> 1.8
diff -u -r1.7 -r1.8
--- tcp_output.c	12 Dec 2004 17:03:01 -0000	1.7
+++ tcp_output.c	12 Dec 2004 17:24:30 -0000	1.8
@@ -708,12 +708,20 @@
 	}
 #endif
         /*
-         * XXX: It seems that osktittcp expect synchronous packet processing
-         * and so our current asynchronous way causes infinite loop. The
-         * ACK flags are normally masked out at the end of this function
+         * XXX: It seems that osktittcp expects that packets are
+         * synchronously processed. The current implementation feeds
+         * oskittcp with the packets asynchronously. That's not a
+         * problem normally when the packets are transfered over
+         * network, but it starts to be a problem when it comes to
+         * loopback packets.
+         * The ACK bits are set in tcp_input which calls tcp_output and
+         * expects them to be cleared before further processing.
+         * Instead tcp_output calls ip_output which produces a packet
+         * and ends up in tcp_input and we're stuck in infinite loop.
+         * Normally the flags are masked out at the end of this function
          * and the incomming packets are processed then, but since 
-         * currently the loopback packet can be received during the 
-         * ip_output call, the function end is never reached.
+         * currently the loopback packet is delivered during the 
+         * ip_output call, the function end is never reached...
          */
 #ifdef __REACTOS__
 	tp->t_flags &= ~(TF_ACKNOW|TF_DELACK);
CVSspam 0.2.8