Commit 0fb370b
committed
flow: Explicitly pad tcp_flags for TCP and tp_dst for IGMP.
'tcp_flags' are not placed at the beginning of the 64-bit block, so
they have to be padded. Today it is done in a hacky way by pushing
zeroes over the last 32-bits of the arp_tha. When that was written
the miniflow_pad_from_64() didn't exist, but it's better to use it
now instead to avoid confusion.
'ct_tp_src/dst' are not actually extracted for IGMP. See the
write_ct_md() function. The pushes are there for the padding purposes,
since 'tp_dst' doesn't end on a 64-bit boundary and so we need to pad
before pushing the IGMP group. Use an explicit padding function
instead to avoid a false impression that IGMP can have non-zero
"ports" in the conntrack tuple.
This change should not change anything functionally.
Acked-by: Paolo Valerio <pvalerio@redhat.com>
Signed-off-by: Ilya Maximets <i.maximets@ovn.org>1 parent cb9e21d commit 0fb370b
1 file changed
+4
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1067 | 1067 | | |
1068 | 1068 | | |
1069 | 1069 | | |
1070 | | - | |
| 1070 | + | |
| 1071 | + | |
1071 | 1072 | | |
1072 | 1073 | | |
1073 | 1074 | | |
| |||
1138 | 1139 | | |
1139 | 1140 | | |
1140 | 1141 | | |
1141 | | - | |
1142 | | - | |
| 1142 | + | |
| 1143 | + | |
1143 | 1144 | | |
1144 | 1145 | | |
1145 | 1146 | | |
| |||
0 commit comments