summaryrefslogtreecommitdiffstats
path: root/lib/Kconfig.kasan
diff options
context:
space:
mode:
authorMaxim Mikityanskiy <maximmi@mellanox.com>2020-10-08 12:34:10 +0300
committerSaeed Mahameed <saeedm@nvidia.com>2020-11-17 11:50:51 -0800
commitea63609857321c38fd4ad096388b413b66001c6c (patch)
tree676cc3b1ee6422e364c872dd6dd733d719a6775e /lib/Kconfig.kasan
parent1b9e2a8c99a5c021041bfb2d512dc3ed92a94ffd (diff)
downloadlinux-stable-ea63609857321c38fd4ad096388b413b66001c6c.tar.gz
linux-stable-ea63609857321c38fd4ad096388b413b66001c6c.tar.bz2
linux-stable-ea63609857321c38fd4ad096388b413b66001c6c.zip
net/mlx5e: Fix refcount leak on kTLS RX resync
On resync, the driver calls inet_lookup_established (__inet6_lookup_established) that increases sk_refcnt of the socket. To decrease it, the driver set skb->destructor to sock_edemux. However, it didn't work well, because the TCP stack also sets this destructor for early demux, and the refcount gets decreased only once, while increased two times (in mlx5e and in the TCP stack). It leads to a socket leak, a TLS context leak, which in the end leads to calling tls_dev_del twice: on socket close and on driver unload, which in turn leads to a crash. This commit fixes the refcount leak by calling sock_gen_put right away after using the socket, thus fixing all the subsequent issues. Fixes: 0419d8c9d8f8 ("net/mlx5e: kTLS, Add kTLS RX resync support") Signed-off-by: Maxim Mikityanskiy <maximmi@mellanox.com> Reviewed-by: Tariq Toukan <tariqt@nvidia.com> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Diffstat (limited to 'lib/Kconfig.kasan')
0 files changed, 0 insertions, 0 deletions