Unused variable warning in do_tcp_setsockopt()

[harshimogalapalli]

BUILDSTDERR: net/ipv4/tcp.c: In function 'do_tcp_setsockopt':
BUILDSTDERR: net/ipv4/tcp.c:2514:14: warning: unused variable 'net' [-Wunused-variable]
BUILDSTDERR: struct net *net = sock_net(sk);

This is only a warning with openela-4.14.y:

commit c3b84f9003a993627adf8fb99f2141488f56381e
Author: Cambda Zhu <cambda@linux.alibaba.com>
Date:   Wed Apr 17 12:24:40 2024 -0400

    net: Replace the limit of TCP_LINGER2 with TCP_FIN_TIMEOUT_MAX

    [ Upstream commit f0628c524fd188c3f9418e12478dfdfadacba815 ]

    This patch changes the behavior of TCP_LINGER2 about its limit. The
    sysctl_tcp_fin_timeout used to be the limit of TCP_LINGER2 but now it's
    only the default value. A new macro named TCP_FIN_TIMEOUT_MAX is added
    as the limit of TCP_LINGER2, which is 2 minutes.

    Since TCP_LINGER2 used sysctl_tcp_fin_timeout as the default value
    and the limit in the past, the system administrator cannot set the
    default value for most of sockets and let some sockets have a greater
    timeout. It might be a mistake that let the sysctl to be the limit of
    the TCP_LINGER2. Maybe we can add a new sysctl to set the max of
    TCP_LINGER2, but FIN-WAIT-2 timeout is usually no need to be too long
    and 2 minutes are legal considering TCP specs.

    Changes in v3:
    - Remove the new socket option and change the TCP_LINGER2 behavior so
      that the timeout can be set to value between sysctl_tcp_fin_timeout
      and 2 minutes.

    Changes in v2:
    - Add int overflow check for the new socket option.

    Changes in v1:
    - Add a new socket option to set timeout greater than
      sysctl_tcp_fin_timeout.

    Signed-off-by: Cambda Zhu <cambda@linux.alibaba.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Stable-dep-of: 9df5335ca974 ("tcp: annotate data-races around tp->linger2")
    Signed-off-by: Sasha Levin <sashal@kernel.org>
    Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>

^^ This backport is causing this warning, doesn't happen on 4.19.y.

Creating this issue for tracking, we will fix this in openela-4.14.346-release

[harshimogalapalli]

This is fixed in 4.14.346-openela release: 7abf8b0

Closing this issue.