diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2020-04-08 20:54:43 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-04-08 14:34:02 -0700 |
| commit | f691a25ce5e5e405156ad4091c8e660b2622b7ad (patch) | |
| tree | 8962d7abb2b2fee1b4aa8198de95f78648816b55 /net | |
| parent | 2abe05234f2e892728c388169631e4b99f354c86 (diff) | |
| download | linux-f691a25ce5e5e405156ad4091c8e660b2622b7ad.tar.gz linux-f691a25ce5e5e405156ad4091c8e660b2622b7ad.tar.bz2 linux-f691a25ce5e5e405156ad4091c8e660b2622b7ad.zip | |
net/tls: fix const assignment warning
Building with some experimental patches, I came across a warning
in the tls code:
include/linux/compiler.h:215:30: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
215 | *(volatile typeof(x) *)&(x) = (val); \
| ^
net/tls/tls_main.c:650:4: note: in expansion of macro 'smp_store_release'
650 | smp_store_release(&saved_tcpv4_prot, prot);
This appears to be a legitimate warning about assigning a const pointer
into the non-const 'saved_tcpv4_prot' global. Annotate both the ipv4 and
ipv6 pointers 'const' to make the code internally consistent.
Fixes: 5bb4c45d466c ("net/tls: Read sk_prot once when building tls proto ops")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
| -rw-r--r-- | net/tls/tls_main.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/net/tls/tls_main.c b/net/tls/tls_main.c index 156efce50dbd..0e989005bdc2 100644 --- a/net/tls/tls_main.c +++ b/net/tls/tls_main.c @@ -56,9 +56,9 @@ enum { TLS_NUM_PROTS, }; -static struct proto *saved_tcpv6_prot; +static const struct proto *saved_tcpv6_prot; static DEFINE_MUTEX(tcpv6_prot_mutex); -static struct proto *saved_tcpv4_prot; +static const struct proto *saved_tcpv4_prot; static DEFINE_MUTEX(tcpv4_prot_mutex); static struct proto tls_prots[TLS_NUM_PROTS][TLS_NUM_CONFIG][TLS_NUM_CONFIG]; static struct proto_ops tls_sw_proto_ops; |