[ros-dev] KBug revision 15386

[WaxDragon]

Yes, this issue has been around since the network breakage last
weekend.  We need our fearless Art to fix it. (If he ever comes back!)
;0)

WD

On 5/17/05, Hartmut Birr <hartmut.birr at gmx.de> wrote:
> James Tabor wrote:
> 
> > Hi,
> > SVB revision 15386,
> >
> It is the same problem like the attached mail.
> 
> - Hartmut
> 
> 
> Subject:
> Re: [ros-dev] Networking
> From:
> Hartmut Birr <hartmut.birr at gmx.de>
> Date:
> Tue, 10 May 2005 22:40:01 +0200
> To:
> ReactOS Development List <ros-dev at reactos.com>
> 
> James Tabor wrote:
> 
> >> Hi WD!
> >> WaxDragon wrote:
> >>
> >
> >>>> You are very likely seeing the same problems I am.  If you have tcpip
> >>>> debugging on, you may see messages like this:
> >>>>
> >
> >> Wow, its funny, ping.exe both of them still resident in memory. I
> >> executed them
> >> minutes before the kernel debugs. Strange stuff!?! 8^o dazed and in
> >> awe, wow can
> >> you see the nice colors!
> >> James
> 
> That's a result of rev 15069. If a irp is created by
> IoBuildDeviceIoControlRequest or IoBuildSynchronousFsdRequest, it must
> be always completed by IoCompleteRequest. The changes from rev. 15069
> bypass a part of IoCompleteRequest if the irp was canceled. The irp is
> still on the threads irp list. A terminated threads waits some time for
> completion of all irps on the thread list. If not all irps are removed,
> ros does  bucheck. While the waiting time,  you can see ping in memory.
> 
> - Hartmut
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
> 
> 
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.com
> http://reactos.com:8080/mailman/listinfo/ros-dev
> 
> 


-- 
"<arty> the tree was touched a lot recently"