All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Kühnel" <thomas.kuehnel@avm.de>,
	"Konstantin Komarov" <almaz.alexandrovich@paragon-software.com>
Cc: kbuild-all@lists.01.org, ntfs3@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	"Thomas Kühnel" <thomas.kuehnel@avm.de>,
	"Nicolas Schier" <n.schier@avm.de>
Subject: Re: [PATCH 2/3] fs/ntfs3: add functions to modify LE bitmaps
Date: Wed, 8 Dec 2021 01:31:15 +0800	[thread overview]
Message-ID: <202112080045.huYZOn4p-lkp@intel.com> (raw)
In-Reply-To: <20211207102454.576906-3-thomas.kuehnel@avm.de>

Hi "Thomas,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1]

url:    https://github.com/0day-ci/linux/commits/Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
base:   0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1
config: arm64-randconfig-s031-20211207 (https://download.01.org/0day-ci/archive/20211208/202112080045.huYZOn4p-lkp@intel.com/config)
compiler: aarch64-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://github.com/0day-ci/linux/commit/2227622e39d3100d10077199481f05ccb9a17204
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
        git checkout 2227622e39d3100d10077199481f05ccb9a17204
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash fs/ntfs3/

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/ntfs3/bitmap.c:1498:37: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned long mask_to_set @@     got restricted __le32 [usertype] @@
   fs/ntfs3/bitmap.c:1498:37: sparse:     expected unsigned long mask_to_set
   fs/ntfs3/bitmap.c:1498:37: sparse:     got restricted __le32 [usertype]
>> fs/ntfs3/bitmap.c:1508:29: sparse: sparse: invalid assignment: &=
>> fs/ntfs3/bitmap.c:1508:29: sparse:    left side has type unsigned long
>> fs/ntfs3/bitmap.c:1508:29: sparse:    right side has type restricted __le32
>> fs/ntfs3/bitmap.c:1518:39: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned long mask_to_clear @@     got restricted __le32 [usertype] @@
   fs/ntfs3/bitmap.c:1518:39: sparse:     expected unsigned long mask_to_clear
   fs/ntfs3/bitmap.c:1518:39: sparse:     got restricted __le32 [usertype]
   fs/ntfs3/bitmap.c:1528:31: sparse: sparse: invalid assignment: &=
   fs/ntfs3/bitmap.c:1528:31: sparse:    left side has type unsigned long
   fs/ntfs3/bitmap.c:1528:31: sparse:    right side has type restricted __le32

vim +1498 fs/ntfs3/bitmap.c

  1492	
  1493	void ntfs_bitmap_set_le(unsigned long *map, unsigned int start, int len)
  1494	{
  1495		unsigned long *p = map + BIT_WORD(start);
  1496		const unsigned int size = start + len;
  1497		int bits_to_set = BITS_PER_LONG - (start % BITS_PER_LONG);
> 1498		unsigned long mask_to_set = cpu_to_le32(BITMAP_FIRST_WORD_MASK(start));
  1499	
  1500		while (len - bits_to_set >= 0) {
  1501			*p |= mask_to_set;
  1502			len -= bits_to_set;
  1503			bits_to_set = BITS_PER_LONG;
  1504			mask_to_set = ~0UL;
  1505			p++;
  1506		}
  1507		if (len) {
> 1508			mask_to_set &= cpu_to_le32(BITMAP_LAST_WORD_MASK(size));
  1509			*p |= mask_to_set;
  1510		}
  1511	}
  1512	
  1513	void ntfs_bitmap_clear_le(unsigned long *map, unsigned int start, int len)
  1514	{
  1515		unsigned long *p = map + BIT_WORD(start);
  1516		const unsigned int size = start + len;
  1517		int bits_to_clear = BITS_PER_LONG - (start % BITS_PER_LONG);
> 1518		unsigned long mask_to_clear = cpu_to_le32(BITMAP_FIRST_WORD_MASK(start));

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 2/3] fs/ntfs3: add functions to modify LE bitmaps
Date: Wed, 08 Dec 2021 01:31:15 +0800	[thread overview]
Message-ID: <202112080045.huYZOn4p-lkp@intel.com> (raw)
In-Reply-To: <20211207102454.576906-3-thomas.kuehnel@avm.de>

[-- Attachment #1: Type: text/plain, Size: 3790 bytes --]

Hi "Thomas,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on 0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1]

url:    https://github.com/0day-ci/linux/commits/Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
base:   0fcfb00b28c0b7884635dacf38e46d60bf3d4eb1
config: arm64-randconfig-s031-20211207 (https://download.01.org/0day-ci/archive/20211208/202112080045.huYZOn4p-lkp(a)intel.com/config)
compiler: aarch64-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://github.com/0day-ci/linux/commit/2227622e39d3100d10077199481f05ccb9a17204
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Thomas-K-hnel/fs-ntfs3-Fixes-for-big-endian-systems/20211207-184206
        git checkout 2227622e39d3100d10077199481f05ccb9a17204
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash fs/ntfs3/

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/ntfs3/bitmap.c:1498:37: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned long mask_to_set @@     got restricted __le32 [usertype] @@
   fs/ntfs3/bitmap.c:1498:37: sparse:     expected unsigned long mask_to_set
   fs/ntfs3/bitmap.c:1498:37: sparse:     got restricted __le32 [usertype]
>> fs/ntfs3/bitmap.c:1508:29: sparse: sparse: invalid assignment: &=
>> fs/ntfs3/bitmap.c:1508:29: sparse:    left side has type unsigned long
>> fs/ntfs3/bitmap.c:1508:29: sparse:    right side has type restricted __le32
>> fs/ntfs3/bitmap.c:1518:39: sparse: sparse: incorrect type in initializer (different base types) @@     expected unsigned long mask_to_clear @@     got restricted __le32 [usertype] @@
   fs/ntfs3/bitmap.c:1518:39: sparse:     expected unsigned long mask_to_clear
   fs/ntfs3/bitmap.c:1518:39: sparse:     got restricted __le32 [usertype]
   fs/ntfs3/bitmap.c:1528:31: sparse: sparse: invalid assignment: &=
   fs/ntfs3/bitmap.c:1528:31: sparse:    left side has type unsigned long
   fs/ntfs3/bitmap.c:1528:31: sparse:    right side has type restricted __le32

vim +1498 fs/ntfs3/bitmap.c

  1492	
  1493	void ntfs_bitmap_set_le(unsigned long *map, unsigned int start, int len)
  1494	{
  1495		unsigned long *p = map + BIT_WORD(start);
  1496		const unsigned int size = start + len;
  1497		int bits_to_set = BITS_PER_LONG - (start % BITS_PER_LONG);
> 1498		unsigned long mask_to_set = cpu_to_le32(BITMAP_FIRST_WORD_MASK(start));
  1499	
  1500		while (len - bits_to_set >= 0) {
  1501			*p |= mask_to_set;
  1502			len -= bits_to_set;
  1503			bits_to_set = BITS_PER_LONG;
  1504			mask_to_set = ~0UL;
  1505			p++;
  1506		}
  1507		if (len) {
> 1508			mask_to_set &= cpu_to_le32(BITMAP_LAST_WORD_MASK(size));
  1509			*p |= mask_to_set;
  1510		}
  1511	}
  1512	
  1513	void ntfs_bitmap_clear_le(unsigned long *map, unsigned int start, int len)
  1514	{
  1515		unsigned long *p = map + BIT_WORD(start);
  1516		const unsigned int size = start + len;
  1517		int bits_to_clear = BITS_PER_LONG - (start % BITS_PER_LONG);
> 1518		unsigned long mask_to_clear = cpu_to_le32(BITMAP_FIRST_WORD_MASK(start));

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

  reply	other threads:[~2021-12-07 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 10:24 [PATCH 0/3] fs/ntfs3: Fixes for big endian systems Thomas Kühnel
2021-12-07 10:24 ` [PATCH 1/3] fs/ntfs3: fix endian conversion in ni_fname_name Thomas Kühnel
2021-12-07 16:00   ` kernel test robot
2021-12-07 16:00     ` kernel test robot
2021-12-09 10:50     ` Thomas Kühnel
2021-12-09 10:50       ` Thomas Kühnel
2021-12-07 10:24 ` [PATCH 2/3] fs/ntfs3: add functions to modify LE bitmaps Thomas Kühnel
2021-12-07 17:31   ` kernel test robot [this message]
2021-12-07 17:31     ` kernel test robot
2021-12-07 10:24 ` [PATCH 3/3] fs/ntfs3: use _le variants of bitops functions Thomas Kühnel
2022-12-30 12:07 ` [PATCH 0/3] fs/ntfs3: Fixes for big endian systems Konstantin Komarov

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=202112080045.huYZOn4p-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=n.schier@avm.de \
    --cc=ntfs3@lists.linux.dev \
    --cc=thomas.kuehnel@avm.de \
    /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.