From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 15652/16110] fs/bcachefs/sb-members.c:422:30: sparse: sparse: incorrect type in assignment (different base types)
Date: Fri, 3 Nov 2023 13:46:33 +0800 [thread overview]
Message-ID: <202311031313.UUxwfuQJ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e27090b1413ff236ca1aec26d6b022149115de2c
commit: 3075aca3c30cf4554dfa67c02113aaf8220348e5 [15652/16110] bcachefs: Add IO error counts to bch_member
config: i386-randconfig-061-20231102 (https://download.01.org/0day-ci/archive/20231103/202311031313.UUxwfuQJ-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231103/202311031313.UUxwfuQJ-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/202311031313.UUxwfuQJ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/bcachefs/sb-members.c: note: in included file:
fs/bcachefs/bcachefs.h:958:9: sparse: sparse: array of flexible structures
>> fs/bcachefs/sb-members.c:422:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 [usertype] errors_reset_time @@ got signed long long @@
fs/bcachefs/sb-members.c:422:30: sparse: expected restricted __le64 [usertype] errors_reset_time
fs/bcachefs/sb-members.c:422:30: sparse: got signed long long
vim +422 fs/bcachefs/sb-members.c
412
413 void bch2_dev_errors_reset(struct bch_dev *ca)
414 {
415 struct bch_fs *c = ca->fs;
416 struct bch_member *m;
417
418 mutex_lock(&c->sb_lock);
419 m = bch2_members_v2_get_mut(c->disk_sb.sb, ca->dev_idx);
420 for (unsigned i = 0; i < ARRAY_SIZE(m->errors_at_reset); i++)
421 m->errors_at_reset[i] = cpu_to_le64(atomic64_read(&ca->errors[i]));
> 422 m->errors_reset_time = ktime_get_real_seconds();
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-03 5:47 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=202311031313.UUxwfuQJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=kmo@daterainc.com \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox