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:2098:16: sparse: sparse: cast to non-scalar
Date: Mon, 29 Sep 2025 16:57:35 +0800 [thread overview]
Message-ID: <202509291645.fcBIaXMb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: e5f0a698b34ed76002dc5cff3804a61c80233a7a
commit: c51da3f7a161c6822232be832abdffe47eb55b4c net: remove sock_i_uid()
date: 3 months ago
config: alpha-randconfig-r122-20250929 (https://download.01.org/0day-ci/archive/20250929/202509291645.fcBIaXMb-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250929/202509291645.fcBIaXMb-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/202509291645.fcBIaXMb-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
net/packet/diag.c: note: in included file (through include/linux/sock_diag.h):
>> include/net/sock.h:2098:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2098:16: sparse: sparse: cast from non-scalar
--
net/packet/af_packet.c:1099:13: sparse: sparse: context imbalance in '__packet_lookup_frame_in_block' - different lock contexts for basic block
net/packet/af_packet.c:2541:17: sparse: sparse: context imbalance in 'tpacket_rcv' - unexpected unlock
net/packet/af_packet.c: note: in included file (through include/net/inet_sock.h, include/net/ip.h):
>> include/net/sock.h:2098:16: sparse: sparse: cast to non-scalar
include/net/sock.h:2098:16: sparse: sparse: cast from non-scalar
vim +2098 include/net/sock.h
^1da177e4c3f415 Linus Torvalds 2005-04-16 2094
e84a4927a404f36 Eric Dumazet 2025-06-20 2095 static inline kuid_t sk_uid(const struct sock *sk)
e84a4927a404f36 Eric Dumazet 2025-06-20 2096 {
e84a4927a404f36 Eric Dumazet 2025-06-20 2097 /* Paired with WRITE_ONCE() in sockfs_setattr() */
e84a4927a404f36 Eric Dumazet 2025-06-20 @2098 return READ_ONCE(sk->sk_uid);
e84a4927a404f36 Eric Dumazet 2025-06-20 2099 }
e84a4927a404f36 Eric Dumazet 2025-06-20 2100
:::::: The code at line 2098 was first introduced by commit
:::::: e84a4927a404f369c842c19de93b216627fcc690 net: annotate races around sk->sk_uid
:::::: TO: Eric Dumazet <edumazet@google.com>
:::::: CC: Jakub Kicinski <kuba@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-09-29 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:57 kernel test robot [this message]
2025-09-29 9:49 ` Eric Dumazet
2025-11-03 8:06 ` Eric Dumazet
2025-11-03 7:26 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=202509291645.fcBIaXMb-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®