tcpdump mailing list archives
Re: TPACKET_V3 timeout bug?
From: Guy Harris <guy () alum mit edu>
Date: Sat, 15 Apr 2017 19:41:46 -0700
On Apr 15, 2017, at 7:10 PM, Andrew Lunn <andrew () lunn ch> wrote:
Do you think this is a kernel problem, libpcap problem, or an application problem?
An application problem. See my response on netdev; the timeout (which is provided by the kernel's capture mechanism, in most cases) is to make sure packets don't stay stuck in the kernel's packet buffer for an indefinite period of time, it's *not* to make sure a thread capturing packets doesn't stay blocked for an indefinite period of time. Whether the timer goes off even if no packets have arrived is platform-dependent; code capturing packets should neither depend on it doing so or on it not doing so. _______________________________________________ tcpdump-workers mailing list tcpdump-workers () lists tcpdump org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Current thread:
- Re: TPACKET_V3 timeout bug? Andrew Lunn (Apr 15)
- Re: TPACKET_V3 timeout bug? Guy Harris (Apr 15)
- Message not available
- Re: TPACKET_V3 timeout bug? Guy Harris (May 02)
- Re: TPACKET_V3 timeout bug? Guy Harris (May 02)
- Message not available
- Message not available
- Message not available
- Re: TPACKET_V3 timeout bug? Guy Harris (May 02)
- Re: TPACKET_V3 timeout bug? Guy Harris (Apr 15)