From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Kent Overstreet <kent.overstreet@linux.dev>
Subject: [bcachefs:bcachefs-testing 204/205] fs/bcachefs/str_hash.c:164:2: warning: label followed by a declaration is a C23 extension
Date: Mon, 9 Dec 2024 18:45:34 +0800 [thread overview]
Message-ID: <202412091807.8PJParb1-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: 48016afd37223fa670a84272ebc9fa0d3122e207
commit: 5ec57ef85d8cb570263a0b01befcd39377a82ade [204/205] bcachefs: bch2_str_hash_check_key() now checks inode hash info
config: arm-randconfig-002-20241209 (https://download.01.org/0day-ci/archive/20241209/202412091807.8PJParb1-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241209/202412091807.8PJParb1-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/202412091807.8PJParb1-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/bcachefs/str_hash.c:3:
In file included from fs/bcachefs/bcachefs.h:188:
In file included from include/linux/bio.h:10:
In file included from include/linux/blk_types.h:10:
In file included from include/linux/bvec.h:10:
In file included from include/linux/highmem.h:8:
In file included from include/linux/cacheflush.h:5:
In file included from arch/arm/include/asm/cacheflush.h:10:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
>> fs/bcachefs/str_hash.c:164:2: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
164 | struct bch_inode_unpacked inode;
| ^
2 warnings generated.
vim +164 fs/bcachefs/str_hash.c
140
141 /*
142 * All versions of the same inode in different snapshots must have the same hash
143 * seed/type: verify that the hash info we're using matches the root
144 */
145 static int check_inode_hash_info_matches_root(struct btree_trans *trans, u64 inum,
146 struct bch_hash_info *hash_info)
147 {
148 struct bch_fs *c = trans->c;
149 struct btree_iter iter;
150 struct bkey_s_c k;
151 int ret = 0;
152
153 for_each_btree_key_reverse_norestart(trans, iter, BTREE_ID_inodes, SPOS(0, inum, U32_MAX),
154 BTREE_ITER_all_snapshots, k, ret) {
155 if (k.k->p.offset != inum)
156 break;
157 if (bkey_is_inode(k.k))
158 goto found;
159 }
160 bch_err(c, "%s(): inum %llu not found", __func__, inum);
161 ret = -BCH_ERR_fsck_repair_unimplemented;
162 goto err;
163 found:
> 164 struct bch_inode_unpacked inode;
165 ret = bch2_inode_unpack(k, &inode);
166 if (ret)
167 goto err;
168
169 struct bch_hash_info hash2 = bch2_hash_info_init(c, &inode);
170 if (memcmp(hash_info, &hash2, sizeof(hash2))) {
171 ret = repair_inode_hash_info(trans, &inode);
172 if (!ret) {
173 bch_err(c, "inode hash info mismatch with root, but mismatch not found");
174 ret = -BCH_ERR_fsck_repair_unimplemented;
175 }
176 }
177 err:
178 bch2_trans_iter_exit(trans, &iter);
179 return ret;
180 }
181
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-09 10:46 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=202412091807.8PJParb1-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=llvm@lists.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.