From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: kbuild-all@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org
Subject: [djwong-xfs:zero-initialize-pmem-5.16 18/28] fs/xfs/libxfs/xfs_ialloc_btree.c:552:53: sparse: sparse: cast truncates bits from constant value (100000000 becomes 0)
Date: Mon, 8 Nov 2021 14:55:19 +0800 [thread overview]
Message-ID: <202111081411.dqXMIqAp-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git zero-initialize-pmem-5.16
head: 34b80c3d1203abd5fd64242ef25898c7d64166ca
commit: c0ef00d1e835bfd24399aaa069b2b608dd60b485 [18/28] xfs: check absolute maximum nlevels for each btree type
config: csky-randconfig-s032-20211008 (attached as .config)
compiler: csky-linux-gcc (GCC) 11.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=c0ef00d1e835bfd24399aaa069b2b608dd60b485
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs zero-initialize-pmem-5.16
git checkout c0ef00d1e835bfd24399aaa069b2b608dd60b485
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=csky SHELL=/bin/bash fs/xfs/ mm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
fs/xfs/libxfs/xfs_ialloc_btree.c: note: in included file (through include/linux/bitops.h, include/linux/kernel.h, include/linux/list.h, ...):
arch/csky/include/asm/bitops.h:77:9: sparse: sparse: preprocessor token __clear_bit redefined
fs/xfs/libxfs/xfs_ialloc_btree.c: note: in included file (through arch/csky/include/asm/bitops.h, include/linux/bitops.h, include/linux/kernel.h, ...):
include/asm-generic/bitops/non-atomic.h:34:9: sparse: this was the original definition
>> fs/xfs/libxfs/xfs_ialloc_btree.c:552:53: sparse: sparse: cast truncates bits from constant value (100000000 becomes 0)
vim +552 fs/xfs/libxfs/xfs_ialloc_btree.c
543
544 unsigned int
545 xfs_inobt_absolute_maxlevels(void)
546 {
547 unsigned int minrecs[2];
548
549 xfs_btree_absolute_minrecs(minrecs, 0, sizeof(xfs_inobt_rec_t),
550 sizeof(xfs_inobt_key_t) + sizeof(xfs_inobt_ptr_t));
551
> 552 return xfs_btree_compute_maxlevels(minrecs, XFS_MAX_AG_INODES);
553 }
554
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 43471 bytes --]
next reply other threads:[~2021-11-08 6:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 6:55 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-10 7:18 kernel test robot
2021-11-09 7:02 kernel test robot
2021-10-22 6:21 kernel test robot
2021-10-08 15:39 kernel test robot
2021-10-08 12:59 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=202111081411.dqXMIqAp-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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®