Page MenuHomeFreeBSD

Handle case when the PCAP file is not set in tcpdump
ClosedPublic

Authored by hselasky on Jun 13 2018, 7:52 AM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 26 2024, 5:07 PM
Unknown Object (File)
Feb 15 2024, 12:27 AM
Unknown Object (File)
Jan 12 2024, 8:48 PM
Unknown Object (File)
Dec 20 2023, 3:19 AM
Unknown Object (File)
Dec 17 2023, 6:07 PM
Unknown Object (File)
Sep 10 2023, 2:09 AM
Unknown Object (File)
Jul 15 2023, 8:29 AM
Unknown Object (File)
Jul 1 2023, 4:53 AM

Details

Summary

Some libpcap backends don't set the PCAP file number.
Make sure we don't trigger a fault when this file number is not set when CASPER and CAPSICUM is enabled.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 17624

Event Timeline

Can you provide any test case for that?

contrib/tcpdump/tcpdump.c
2073

VFileName at this point must be equals to NULL.

Can you provide any test case for that?

tcpdump -i mlx5_0

Given you have a mlx5 compatible PCI device and mlx5en/mlx5ib loaded.

oshogbo added inline comments.
contrib/tcpdump/tcpdump.c
2073

I think I would just do that in first case. Because the other cansandbox depends on the HAVING CASPER or not.
Otherwise LGTM.

This revision is now accepted and ready to land.Jun 26 2018, 8:06 PM