All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android-mainline-desktop 1/1] drivers/misc/uid_sys_stats.c:38:12: sparse: sparse: symbol 'uid_lock' was not declared. Should it be static?
Date: Wed, 18 Nov 2026 05:39:22 +0100	[thread overview]
Message-ID: <20261118053742.bbC3d0Qf-lkp@intel.com> (raw)

Hi Neill,

First bad commit (maybe != root cause):

tree:   https://android.googlesource.com/kernel/common android-mainline-desktop
head:   8c75ea48a76401ef6e5d894fe15befd2e4d6e1e8
commit: 4a5826e549a3bd3bc3d81e19a1e2420f5f2070ef [1/1] Revert "ANDROID: disble the UID_SYS_STATS driver"
config: x86_64-randconfig-r2304-20261118 (https://download.01.org/0day-ci/archive/20261118/20261118053742.bbC3d0Qf-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261118/20261118053742.bbC3d0Qf-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/20261118053742.bbC3d0Qf-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/misc/uid_sys_stats.c:38:12: sparse: sparse: symbol 'uid_lock' was not declared. Should it be static?

vim +/uid_lock +38 drivers/misc/uid_sys_stats.c

3669a3205af35a5 Neill Kapron 2023-05-08  31  
12788836b1f36ef Jin Qian     2015-03-11  32  #define UID_HASH_BITS	10
b6115e140102a29 Peifeng Li   2023-04-13  33  #define UID_HASH_NUMS	(1 << UID_HASH_BITS)
12788836b1f36ef Jin Qian     2015-03-11 @34  DECLARE_HASHTABLE(hash_table, UID_HASH_BITS);
b6115e140102a29 Peifeng Li   2023-04-13  35  /*
b6115e140102a29 Peifeng Li   2023-04-13  36   * uid_lock[bkt] ensure consistency of hash_table[bkt]
b6115e140102a29 Peifeng Li   2023-04-13  37   */
b6115e140102a29 Peifeng Li   2023-04-13 @38  spinlock_t uid_lock[UID_HASH_NUMS];
12788836b1f36ef Jin Qian     2015-03-11  39  

:::::: The code at line 38 was first introduced by commit
:::::: b6115e140102a290143ec02a3a2b3d5aec506b3a ANDROID: uid_sys_stat: split the global lock uid_lock to the fine-grained locks for each hlist in hash_table.

:::::: TO: Peifeng Li <lipeifeng@oppo.com>
:::::: CC: Neill Kapron <nkapron@google.com>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-11-18  4:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261118053742.bbC3d0Qf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.