From: kernel test robot <lkp@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Jakub Kicinski" <kuba@kernel.org>,
"Maciej Żenczykowski" <maze@google.com>
Subject: include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
Date: Sat, 6 Dec 2025 18:09:51 +0800 [thread overview]
Message-ID: <202512061811.TwIhRj4D-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 416f99c3b16f582a3fc6d64a1f77f39d94b76de5
commit: e84a4927a404f369c842c19de93b216627fcc690 net: annotate races around sk->sk_uid
date: 6 months ago
config: arm64-randconfig-r121-20251206 (https://download.01.org/0day-ci/archive/20251206/202512061811.TwIhRj4D-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 14bf95b06a18b9b59c89601cbc0e5a6f2176b118)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251206/202512061811.TwIhRj4D-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202512061811.TwIhRj4D-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/ipv6/af_inet6.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h, include/linux/icmpv6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/datagram.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/ping.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h, include/net/addrconf.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/inet6_connection_sock.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/raw.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h, include/linux/icmpv6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/tcp_ipv6.c: note: in included file (through include/linux/tcp.h, include/linux/ipv6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
net/ipv6/tcp_ipv6.c:1565:25: sparse: sparse: context imbalance in 'tcp_v6_syn_recv_sock' - unexpected unlock
net/ipv6/tcp_ipv6.c:1956:21: sparse: sparse: context imbalance in 'tcp_v6_rcv' - different lock contexts for basic block
--
net/ipv6/udp.c: note: in included file (through include/linux/bpf-cgroup.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
--
net/ipv6/route.c:2382:39: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] flow_label @@ got restricted __be32 @@
net/ipv6/route.c:2382:39: sparse: expected unsigned int [usertype] flow_label
net/ipv6/route.c:2382:39: sparse: got restricted __be32
net/ipv6/route.c: note: in included file (through include/linux/mroute_base.h, include/linux/mroute6.h):
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
>> include/net/sock.h:2100:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2100:16: sparse: sparse: cast from non-scalar
vim +2100 include/net/sock.h
2096
2097 static inline kuid_t sk_uid(const struct sock *sk)
2098 {
2099 /* Paired with WRITE_ONCE() in sockfs_setattr() */
> 2100 return READ_ONCE(sk->sk_uid);
2101 }
2102
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-06 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 10:09 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-10 21:06 kernel test robot
2026-01-10 22:15 ` Al Viro
2026-01-10 22:35 ` Al Viro
2026-01-11 10:08 ` Eric Dumazet
2026-01-12 12:33 ` Peter Zijlstra
2026-01-11 18:20 ` Al Viro
2026-01-11 18:51 ` Al Viro
2026-01-12 12:37 ` Peter Zijlstra
2026-01-12 15:02 ` Will Deacon
2026-01-12 19:21 ` Al Viro
2026-01-12 21:16 ` Al Viro
2026-01-12 22:39 ` David Laight
2026-01-13 0:28 ` Al Viro
2026-01-12 12:32 ` Peter Zijlstra
2026-01-12 19:30 ` Al Viro
2026-01-13 15:27 ` Peter Zijlstra
2026-01-12 0:49 ` Philip Li
2025-08-25 4:45 kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202512061811.TwIhRj4D-lkp@intel.com \
--to=lkp@intel.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maze@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®