From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:master 36/38] fs/bcachefs/recovery_passes.c:120:16: sparse: sparse: incorrect type in initializer (different base types)
Date: Mon, 1 Apr 2024 01:27:21 +0800 [thread overview]
Message-ID: <202404010140.vvxpncUw-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git master
head: a097468ffe82f16528ddb9ed6ae95baacf633858
commit: c298bc7b038f31ad189069bb146e8f935c508500 [36/38] bcachefs: bch2_run_explicit_recovery_pass_persistent()
config: x86_64-randconfig-121-20240331 (https://download.01.org/0day-ci/archive/20240401/202404010140.vvxpncUw-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240401/202404010140.vvxpncUw-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/202404010140.vvxpncUw-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/bcachefs/recovery_passes.c: note: in included file:
fs/bcachefs/bcachefs.h:1023:9: sparse: sparse: array of flexible structures
>> fs/bcachefs/recovery_passes.c:120:16: sparse: sparse: incorrect type in initializer (different base types) @@ expected unsigned long long [usertype] s @@ got restricted __le64 [usertype] @@
fs/bcachefs/recovery_passes.c:120:16: sparse: expected unsigned long long [usertype] s
fs/bcachefs/recovery_passes.c:120:16: sparse: got restricted __le64 [usertype]
>> fs/bcachefs/recovery_passes.c:125:44: sparse: sparse: restricted __le64 degrades to integer
>> fs/bcachefs/recovery_passes.c:126:50: sparse: sparse: invalid assignment: |=
fs/bcachefs/recovery_passes.c:126:50: sparse: left side has type restricted __le64
fs/bcachefs/recovery_passes.c:126:50: sparse: right side has type unsigned long long
fs/bcachefs/recovery_passes.c:43:9: sparse: sparse: self-comparison always evaluates to false
vim +120 fs/bcachefs/recovery_passes.c
116
117 int bch2_run_explicit_recovery_pass_persistent(struct bch_fs *c,
118 enum bch_recovery_pass pass)
119 {
> 120 u64 s =cpu_to_le64(bch2_recovery_passes_to_stable(BIT_ULL(pass)));
121
122 mutex_lock(&c->sb_lock);
123 struct bch_sb_field_ext *ext = bch2_sb_field_get(c->disk_sb.sb, ext);
124
> 125 if (!(ext->recovery_passes_required[0] & s)) {
> 126 ext->recovery_passes_required[0] |= s;
127 bch2_write_super(c);
128 }
129 mutex_unlock(&c->sb_lock);
130
131 return bch2_run_explicit_recovery_pass(c, pass);
132 }
133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-31 17:27 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=202404010140.vvxpncUw-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--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.