diff options
| author | Or Gerlitz | 2018-03-13 20:43:43 +0100 |
|---|---|---|
| committer | Saeed Mahameed | 2018-03-26 22:58:48 +0200 |
| commit | 423c9db29943cfc43e3a408192e9efa4178af6a1 (patch) | |
| tree | 50f6c81a73a24b91a913e72db8145e046afe8cf9 /drivers/net/ethernet/mellanox/mlx5/core/en_main.c | |
| parent | net/mlx5e: Fix memory usage issues in offloading TC flows (diff) | |
| download | kernel-qcow2-linux-423c9db29943cfc43e3a408192e9efa4178af6a1.tar.gz kernel-qcow2-linux-423c9db29943cfc43e3a408192e9efa4178af6a1.tar.xz kernel-qcow2-linux-423c9db29943cfc43e3a408192e9efa4178af6a1.zip | |
net/mlx5e: Avoid using the ipv6 stub in the TC offload neigh update path
Currently we use the global ipv6_stub var to access the ipv6 global
nd table. This practice gets us to troubles when the stub is only partially
set e.g when ipv6 is loaded under the disabled policy. In this case, as of commit
343d60aada5a ("ipv6: change ipv6_stub_impl.ipv6_dst_lookup to take net argument")
the stub is not null, but stub->nd_tbl is and we crash.
As we can access the ipv6 nd_tbl directly, the fix is just to avoid the
reference through the stub. There is one place in the code where we
issue ipv6 route lookup and keep doing it through the stub, but that
mentioned commit makes sure we get -EAFNOSUPPORT from the stack.
Fixes: 232c001398ae ("net/mlx5e: Add support to neighbour update flow")
Signed-off-by: Or Gerlitz <ogerlitz@mellanox.com>
Reviewed-by: Aviv Heller <avivh@mellanox.com>
Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
Diffstat (limited to 'drivers/net/ethernet/mellanox/mlx5/core/en_main.c')
0 files changed, 0 insertions, 0 deletions