summaryrefslogtreecommitdiff
path: root/net/ax25
diff options
context:
space:
mode:
authorPatrick McHardy <kaber@trash.net>2013-04-05 20:42:05 +0200
committerBen Hutchings <ben@decadent.org.uk>2013-05-13 15:02:36 +0100
commit08d849ac4e7717d1d9ad4a442432d176df44ae43 (patch)
tree7c3cd2845b7ea747e14072f2cadd701e3891a45e /net/ax25
parent171a68064def4bf3cbd4cda16664bf1de515c649 (diff)
netfilter: don't reset nf_trace in nf_reset()
[ Upstream commit 124dff01afbdbff251f0385beca84ba1b9adda68 ] Commit 130549fe ("netfilter: reset nf_trace in nf_reset") added code to reset nf_trace in nf_reset(). This is wrong and unnecessary. nf_reset() is used in the following cases: - when passing packets up the the socket layer, at which point we want to release all netfilter references that might keep modules pinned while the packet is queued. nf_trace doesn't matter anymore at this point. - when encapsulating or decapsulating IPsec packets. We want to continue tracing these packets after IPsec processing. - when passing packets through virtual network devices. Only devices on that encapsulate in IPv4/v6 matter since otherwise nf_trace is not used anymore. Its not entirely clear whether those packets should be traced after that, however we've always done that. - when passing packets through virtual network devices that make the packet cross network namespace boundaries. This is the only cases where we clearly want to reset nf_trace and is also what the original patch intended to fix. Add a new function nf_reset_trace() and use it in dev_forward_skb() to fix this properly. Signed-off-by: Patrick McHardy <kaber@trash.net> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'net/ax25')
0 files changed, 0 insertions, 0 deletions