Segmentation fault when running 'flow' with wrong arguments
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
Fix Committed
|
Medium
|
Kumar Harsh | |||
R4.0 |
Won't Fix
|
Medium
|
Kumar Harsh | |||
R4.1 |
Fix Committed
|
Medium
|
Kumar Harsh | |||
R5.0 |
Fix Committed
|
Medium
|
Kumar Harsh | |||
Trunk |
Fix Committed
|
Medium
|
Kumar Harsh |
Bug Description
Hi everybody,
When running the flow utility on a compute node with a malformed matching filter expression, a segmentation fault occurs, e.g.:
# flow --match "& 10.2.1.1"
Segmentation fault
or:
# flow --match ", "
Segmentation fault
I am using opencontrail 3.2.6 running in a setup with 1 Openstack (newton) node, 1 Contrail controller and 2 compute nodes. However, the flow table is empty (or, actually, does not matter):
# flow -l
Flow table(size 80609280, entries 629760)
Entries: Created 0 Added 0 Deleted 0 Changed 0 Processed 0 Used Overflow entries 0
(Created Flows/CPU: 0 0 0 0)(oflows 0)
Action:F=Forward, D=Drop N=NAT(S=SNAT, D=DNAT, Ps=SPAT, Pd=DPAT, L=Link Local Port)
Other:
Flags:E=Evicted, Ec=Evict Candidate, N=New Flow, M=Modified Dm=Delete Marked
TCP(r=reverse)
Index Source:
-------
#
Thanks,
Andrei
tags: | added: analytics |
tags: |
added: vrouter removed: analytics |
Changed in opencontrail: | |
assignee: | nobody → Kumar Harsh (hkumar) |
no longer affects: | opencontrail |
Review in progress for https:/ /review. opencontrail. org/45003
Submitter: Kumar Harsh (<email address hidden>)