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 172/174] fs/bcachefs/dirent.h:46:23: error: use of undeclared identifier 'c'
Date: Wed, 16 Jul 2025 00:55:42 +0800 [thread overview]
Message-ID: <202507160030.SxpLU2RF-lkp@intel.com> (raw)
tree: https://evilpiepirate.org/git/bcachefs.git bcachefs-testing
head: a6e8423df525d9fb1d0feff091aff2a0d86c5ffd
commit: 6db4e8f88c74a40e7b09ea9c7d862c54c3c75bce [172/174] fixup! bcachefs: Allow CONFIG_UNICODE=m
config: i386-buildonly-randconfig-005-20250715 (https://download.01.org/0day-ci/archive/20250716/202507160030.SxpLU2RF-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250716/202507160030.SxpLU2RF-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/202507160030.SxpLU2RF-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/bcachefs/fs.c:10:
>> fs/bcachefs/dirent.h:46:23: error: use of undeclared identifier 'c'
46 | return bch_err_throw(c, no_casefolding_without_utf8);
| ^
fs/bcachefs/fs.c:1108:3: error: cannot jump from this goto statement to its label
1108 | goto err;
| ^
fs/bcachefs/fs.c:1110:21: note: jump bypasses initialization of variable with __attribute__((cleanup))
1110 | CLASS(btree_trans, trans)(c);
| ^
2 errors generated.
--
In file included from fs/bcachefs/inode.c:10:
>> fs/bcachefs/dirent.h:46:23: error: use of undeclared identifier 'c'
46 | return bch_err_throw(c, no_casefolding_without_utf8);
| ^
1 error generated.
vim +/c +46 fs/bcachefs/dirent.h
25
26 #if IS_ENABLED(CONFIG_UNICODE)
27 int bch2_casefold(struct btree_trans *, const struct bch_hash_info *,
28 const struct qstr *, struct qstr *);
29
30 static inline int bch2_maybe_casefold(struct btree_trans *trans,
31 const struct bch_hash_info *info,
32 const struct qstr *str, struct qstr *out_cf)
33 {
34 if (likely(!info->cf_encoding)) {
35 *out_cf = *str;
36 return 0;
37 } else {
38 return bch2_casefold(trans, info, str, out_cf);
39 }
40 }
41 #else
42 static inline int bch2_maybe_casefold(struct btree_trans *trans,
43 const struct bch_hash_info *info,
44 const struct qstr *str, struct qstr *out_cf)
45 {
> 46 return bch_err_throw(c, no_casefolding_without_utf8);
47 }
48 #endif
49
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-15 16:56 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=202507160030.SxpLU2RF-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).