aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorDavid S. Miller <[email protected]>2015-08-29 13:07:55 -0700
committerDavid S. Miller <[email protected]>2015-08-29 13:07:55 -0700
commit6d74232410a9f3ed0e1fc0f5e538598f21e93982 (patch)
tree388c9e94c26bdd40875562a58b84a54213ca7ac7 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentf6d3c19274c74ff17174df8078e0a14df003667f (diff)
parenta43a9ef6a2e510fec61176ff2c34fab3e7d581da (diff)
Merge branch 'tnl-ipv4-ipv6'
Jiri Benc says: ==================== tunnels: fix incorrect IPv4/v6 headers interpretation With tunneling, it is currently possible to get an IPv6 header and interpret it as an IPv4 header, or to interpret an IPv6 address as an IPv4 address (and vice versa). This leads to things like sending packets to incorrect address, IPv6 flow label being interpreted as IP packet length, etc. Fix several places where this can happen. Most of this is net-next only. The third patch affects net, too, but it doesn't seem there's anything in user space that sets the attribute at all currently, thus net-next is fine. Changelog: v2: fixed geneve after incorrect rebase on top of Pravin's patches ==================== Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions