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:bcachefs-testing 122/123] fs/bcachefs/extents_format.h:219:33: error: width of 'flags' exceeds its type
Date: Wed, 26 Feb 2025 17:57:09 +0800 [thread overview]
Message-ID: <202502261700.DcbApKEF-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: 8de504fc059b751ae0cc0fd600f2d5e28ccb8dc5
commit: 82af8187566114f55114f1b878562de031e0b9b4 [122/123] bcachefs: bcachefs_metadata_version_extent_flags
config: arm64-randconfig-002-20250226 (https://download.01.org/0day-ci/archive/20250226/202502261700.DcbApKEF-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250226/202502261700.DcbApKEF-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/202502261700.DcbApKEF-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/bcachefs/bcachefs_format.h:502,
from fs/bcachefs/bcachefs.h:208,
from fs/bcachefs/bkey_sort.c:2:
>> fs/bcachefs/extents_format.h:219:33: error: width of 'flags' exceeds its type
219 | __u64 flags:76
| ^~~~~
>> fs/bcachefs/extents_format.h:220:33: error: expected ',', ';' or '}' before 'type'
220 | type:7;
| ^~~~
--
In file included from fs/bcachefs/bcachefs_format.h:502,
from fs/bcachefs/bcachefs.h:208,
from fs/bcachefs/extents.c:9:
>> fs/bcachefs/extents_format.h:219:33: error: width of 'flags' exceeds its type
219 | __u64 flags:76
| ^~~~~
>> fs/bcachefs/extents_format.h:220:33: error: expected ',', ';' or '}' before 'type'
220 | type:7;
| ^~~~
fs/bcachefs/extents.c: In function 'bch2_bkey_extent_flags_set':
>> fs/bcachefs/extents.c:1476:26: error: 'struct bch_extent_flags' has no member named 'type'
1476 | .type = BIT(BCH_EXTENT_ENTRY_flags),
| ^~~~
fs/bcachefs/extents.c:1477:35: warning: initialized field overwritten [-Woverride-init]
1477 | .flags = flags,
| ^~~~~
fs/bcachefs/extents.c:1477:35: note: (near initialization for 'f.flags')
vim +/flags +219 fs/bcachefs/extents_format.h
213
214 struct bch_extent_flags {
215 #if defined(__LITTLE_ENDIAN_BITFIELD)
216 __u64 type:7,
217 flags:57;
218 #elif defined (__BIG_ENDIAN_BITFIELD)
> 219 __u64 flags:76
> 220 type:7;
221 #endif
222 };
223
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-26 9:57 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=202502261700.DcbApKEF-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.