All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [koverstreet-bcachefs:bcachefs-rebalance_v2 465/799] fs/bcachefs/data/extents.h:551:9: sparse: sparse: unsigned value that used to be signed checked against zero?
Date: Wed, 24 Dec 2025 23:09:28 +0800	[thread overview]
Message-ID: <202512242348.gvV7rBbQ-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence static check warning: fs/bcachefs/data/extents.h:551:9: sparse: sparse: unsigned value that used to be signed checked against zero?"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Kent Overstreet <kent.overstreet@linux.dev>

tree:   https://github.com/koverstreet/bcachefs bcachefs-rebalance_v2
head:   d4b3d00447faf8d4d95db47e3902e4ca4db8fbdc
commit: 78e53242d57830619d4964261dda9934f4d18c47 [465/799] bcachefs: move data code to subdir
:::::: branch date: 7 weeks ago
:::::: commit date: 9 weeks ago
config: riscv-randconfig-r133-20251222 (https://download.01.org/0day-ci/archive/20251224/202512242348.gvV7rBbQ-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 185f5fd5ce4c65116ca8cf6df467a682ef090499)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251224/202512242348.gvV7rBbQ-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/r/202512242348.gvV7rBbQ-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   WARNING: invalid argument to '-march': '_zacas_zabha'
   fs/bcachefs/fs-io.c: note: in included file (through fs/bcachefs/alloc/buckets.h):
>> fs/bcachefs/data/extents.h:551:9: sparse: sparse: unsigned value that used to be signed checked against zero?
   fs/bcachefs/fs-io.c:748:16: sparse: signed value source
>> fs/bcachefs/data/extents.h:551:9: sparse: sparse: unsigned value that used to be signed checked against zero?
   fs/bcachefs/fs-io.c:748:16: sparse: signed value source
--
   WARNING: invalid argument to '-march': '_zacas_zabha'
>> fs/bcachefs/data/copygc.c:440:21: sparse: sparse: incompatible types in comparison expression (different address spaces):
   fs/bcachefs/data/copygc.c:440:21: sparse:    struct task_struct [noderef] __rcu *
   fs/bcachefs/data/copygc.c:440:21: sparse:    struct task_struct *
--
   WARNING: invalid argument to '-march': '_zacas_zabha'
   fs/bcachefs/opts.c: note: in included file:
>> fs/bcachefs/data/copygc.h:11:33: sparse: sparse: incompatible types in comparison expression (different address spaces):
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct [noderef] __rcu *
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct *
--
   WARNING: invalid argument to '-march': '_zacas_zabha'
   fs/bcachefs/recovery_passes.c:341:5: sparse: sparse: context imbalance in '__bch2_run_explicit_recovery_pass' - wrong count at exit
   fs/bcachefs/recovery_passes.c: note: in included file:
>> fs/bcachefs/data/copygc.h:11:33: sparse: sparse: incompatible types in comparison expression (different address spaces):
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct [noderef] __rcu *
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct *
--
   WARNING: invalid argument to '-march': '_zacas_zabha'
   fs/bcachefs/recovery.c: note: in included file (through fs/bcachefs/bcachefs.h):
   fs/bcachefs/bcachefs_format.h:633:38: sparse: sparse: array of flexible structures
   fs/bcachefs/bcachefs_format.h:1326:38: sparse: sparse: array of flexible structures
   fs/bcachefs/recovery.c: note: in included file:
>> fs/bcachefs/data/copygc.h:11:33: sparse: sparse: incompatible types in comparison expression (different address spaces):
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct [noderef] __rcu *
   fs/bcachefs/data/copygc.h:11:33: sparse:    struct task_struct *

vim +551 fs/bcachefs/data/extents.h

1c6fdbd8f2465d fs/bcachefs/extents.h Kent Overstreet 2017-03-16  546  
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  547  static inline bool bkey_extent_is_unwritten(struct bkey_s_c k)
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  548  {
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  549  	struct bkey_ptrs_c ptrs = bch2_bkey_ptrs_c(k);
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  550  
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13 @551  	bkey_for_each_ptr(ptrs, ptr)
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  552  		if (ptr->unwritten)
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  553  			return true;
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  554  	return false;
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  555  }
792031116bee35 fs/bcachefs/extents.h Kent Overstreet 2022-11-13  556  

:::::: The code at line 551 was first introduced by commit
:::::: 792031116bee35e13be7c8ae8cf1b8eec141b136 bcachefs: Unwritten extents support

:::::: TO: Kent Overstreet <kent.overstreet@linux.dev>
:::::: CC: Kent Overstreet <kent.overstreet@linux.dev>

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

             reply	other threads:[~2025-12-24 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 15:09 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-26 21:05 [koverstreet-bcachefs:bcachefs-rebalance_v2 465/799] fs/bcachefs/data/extents.h:551:9: sparse: sparse: unsigned value that used to be signed checked against zero? kernel test robot
2026-05-15 17:18 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=202512242348.gvV7rBbQ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.