[Bug 297341] net-mgmt/yaf: 2.19.3 crashes
[email protected] Fri, 07 Aug 2026 18:43:44 +0000
| Newsgroups | gmane.os.freebsd.devel.ports.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297341
Bug ID: 297341
Summary: net-mgmt/yaf: 2.19.3 crashes
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Flags: maintainer-feedback?([email protected])
CC: [email protected]
On our flow sensor, yaf 2.19.3 crashes about once per cpu-minute. A freshly
built 2.13.0_1 package does not crash.
We are invoking yaf with:
daemon -r -o /var/log/yaf.log yaf --in ix1 --live pcap --out 10.0.0.2
--ipfix-port 18000 --ipfix tcp --silk --verbose --max-payload 256 --flow-stats
--become-user nobody --become-group nobody --active-timeout 60 --idle-timeout
60 --stats 60 --max-payload=384 --applabel
The 2.19.3 binary crashes with:
pid 14123 (yaf), jid 0, uid 65534: exited on signal 11 (no core dump - bad
address)
Attaching lldb to a running process and waiting for it to crash shows that the
segfault occurs somewhere in the deep packet inspection code, but no obvious
smoking gun. The fault address was indicative of a null pointer struct member
dereference (address in first page of virtual address space). The crash is
apparently traffic-dependent.
Happy to do more debugging if I can get some pointers as to what would be
helpful.
--
You are receiving this mail because:
You are the assignee for the bug.