diff options
| author | Florian Westphal <[email protected]> | 2016-10-29 03:01:50 +0200 |
|---|---|---|
| committer | Pablo Neira Ayuso <[email protected]> | 2016-11-08 23:53:36 +0100 |
| commit | fb9c9649a1d0a65a8f94f784aa18252a0dd584c1 (patch) | |
| tree | 64f04efbfbc06e963cdc37e6ac22da7f33fe7808 /scripts/gcc-plugins/cyc_complexity_plugin.c | |
| parent | 8fbfef7f505bba60fb57078b7621270ee57cd1c4 (diff) | |
netfilter: connmark: ignore skbs with magic untracked conntrack objects
The (percpu) untracked conntrack entries can end up with nonzero connmarks.
The 'untracked' conntrack objects are merely a way to distinguish INVALID
(i.e. protocol connection tracker says payload doesn't meet some
requirements or packet was never seen by the connection tracking code)
from packets that are intentionally not tracked (some icmpv6 types such as
neigh solicitation, or by using 'iptables -j CT --notrack' option).
Untracked conntrack objects are implementation detail, we might as well use
invalid magic address instead to tell INVALID and UNTRACKED apart.
Check skb->nfct for untracked dummy and behave as if skb->nfct is NULL.
Reported-by: XU Tianwen <[email protected]>
Signed-off-by: Florian Westphal <[email protected]>
Signed-off-by: Pablo Neira Ayuso <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/cyc_complexity_plugin.c')
0 files changed, 0 insertions, 0 deletions