[Winpcap-bugs] potential bug in WinPCap can cause system hang

Gianluca Varenni gianluca.varenni at cacetech.com
Fri May 9 16:12:24 GMT 2008


Sebastian,

I've added your code in our source base (with a note). However the kernel 
dump feature (where that code comes from) has been disabled long time ago, 
it's basically dead code. We keep it in case the feature will be re-enabled 
(and probably rewritten and reviewed from scratch) in the future.

Have a nice day
GV

----- Original Message ----- 
From: "Sebastian Gottschalk" <seppig_relay at gmx.de>
To: <winpcap-bugs at winpcap.org>
Sent: Wednesday, May 07, 2008 4:55 PM
Subject: [Winpcap-bugs] potential bug in WinPCap can cause system hang


> Hello there.
>
> The issue is within dump.c!PacketDumpCompletion. As an I/O completion 
> routine it is bound to the contract that every pending IRP passed to this 
> routine has to be marked as pending in case that is wasn't yet. Since the 
> device returning this IRP is a filesystem device (PacketDumpCompletion is 
> setup by WriteDumpFile), such cases might happen and would then hang the 
> filesystem, soon hanging up then entire system.
>
> Solution:
>
> if (Irp->PendingReturned)
> IoMarkIrpPending(Irp);
>
>
> Greetings,
> Sebastian Gottschalk
> _______________________________________________
> Winpcap-bugs mailing list
> Winpcap-bugs at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-bugs 



More information about the Winpcap-bugs mailing list