From: kernel test robot <lkp@intel.com>
To: Asahi Lina <lina@asahilina.net>
Cc: oe-kbuild-all@lists.linux.dev, Janne Grunau <j@jannau.net>
Subject: [asahilinux:bits/030-misc 12/16] kernel/locking/lockdep.c:3407:49: sparse: sparse: cast truncates bits from constant value (a0000 becomes 0)
Date: Sun, 10 May 2026 06:42:16 +0800 [thread overview]
Message-ID: <202605100659.Q44ovXIS-lkp@intel.com> (raw)
tree: https://github.com/AsahiLinux/linux bits/030-misc
head: ba55a7ab0f6380bbedb1480e837abed687c987dd
commit: 033daad0e3013ea11037cd3d33a22d082a8102f3 [12/16] Increase MAX_LOCKDEP_CHAIN_HLOCKS
config: s390-randconfig-r122-20260509 (https://download.01.org/0day-ci/archive/20260510/202605100659.Q44ovXIS-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260510/202605100659.Q44ovXIS-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/202605100659.Q44ovXIS-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/locking/lockdep.c:3407:49: sparse: sparse: cast truncates bits from constant value (a0000 becomes 0)
>> kernel/locking/lockdep.c:3407:49: sparse: sparse: cast truncates bits from constant value (a0000 becomes 0)
vim +3407 kernel/locking/lockdep.c
810507fe6fd5ff Waiman Long 2020-02-06 3399
810507fe6fd5ff Waiman Long 2020-02-06 3400 static inline void init_chain_block(int offset, int next, int bucket, int size)
810507fe6fd5ff Waiman Long 2020-02-06 3401 {
810507fe6fd5ff Waiman Long 2020-02-06 3402 chain_hlocks[offset] = (next >> 16) | CHAIN_BLK_FLAG;
810507fe6fd5ff Waiman Long 2020-02-06 3403 chain_hlocks[offset + 1] = (u16)next;
810507fe6fd5ff Waiman Long 2020-02-06 3404
810507fe6fd5ff Waiman Long 2020-02-06 3405 if (size && !bucket) {
810507fe6fd5ff Waiman Long 2020-02-06 3406 chain_hlocks[offset + 2] = size >> 16;
810507fe6fd5ff Waiman Long 2020-02-06 @3407 chain_hlocks[offset + 3] = (u16)size;
810507fe6fd5ff Waiman Long 2020-02-06 3408 }
810507fe6fd5ff Waiman Long 2020-02-06 3409 }
810507fe6fd5ff Waiman Long 2020-02-06 3410
:::::: The code at line 3407 was first introduced by commit
:::::: 810507fe6fd5ff3de429121adff49523fabb643a locking/lockdep: Reuse freed chain_hlocks entries
:::::: TO: Waiman Long <longman@redhat.com>
:::::: CC: Ingo Molnar <mingo@kernel.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-09 22:42 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=202605100659.Q44ovXIS-lkp@intel.com \
--to=lkp@intel.com \
--cc=j@jannau.net \
--cc=lina@asahilina.net \
--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.