From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/common 5/5] fs/f2fs/dir.c:370:35: error: use of undeclared identifier 'inode'
Date: Fri, 28 Mar 2025 18:06:42 +0800 [thread overview]
Message-ID: <202503281735.NGPfccfP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
head: 221d9fea44a3b5a03030a89853dfb5e78a1cdc9f
commit: 221d9fea44a3b5a03030a89853dfb5e78a1cdc9f [5/5] f2fs: support to disable linear lookup fallback
config: hexagon-randconfig-002-20250328 (https://download.01.org/0day-ci/archive/20250328/202503281735.NGPfccfP-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250328/202503281735.NGPfccfP-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/202503281735.NGPfccfP-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/f2fs/dir.c:370:35: error: use of undeclared identifier 'inode'
!sb_no_casefold_compat_fallback(inode->i_sb)) {
^
1 error generated.
vim +/inode +370 fs/f2fs/dir.c
329
330 struct f2fs_dir_entry *__f2fs_find_entry(struct inode *dir,
331 const struct f2fs_filename *fname,
332 struct page **res_page)
333 {
334 unsigned long npages = dir_blocks(dir);
335 struct f2fs_dir_entry *de = NULL;
336 unsigned int max_depth;
337 unsigned int level;
338 bool use_hash = true;
339
340 *res_page = NULL;
341
342 #if IS_ENABLED(CONFIG_UNICODE)
343 start_find_entry:
344 #endif
345 if (f2fs_has_inline_dentry(dir)) {
346 de = f2fs_find_in_inline_dir(dir, fname, res_page, use_hash);
347 goto out;
348 }
349
350 if (npages == 0)
351 goto out;
352
353 max_depth = F2FS_I(dir)->i_current_depth;
354 if (unlikely(max_depth > MAX_DIR_HASH_DEPTH)) {
355 f2fs_warn(F2FS_I_SB(dir), "Corrupted max_depth of %lu: %u",
356 dir->i_ino, max_depth);
357 max_depth = MAX_DIR_HASH_DEPTH;
358 f2fs_i_depth_write(dir, max_depth);
359 }
360
361 for (level = 0; level < max_depth; level++) {
362 de = find_in_level(dir, level, fname, res_page, use_hash);
363 if (de || IS_ERR(*res_page))
364 break;
365 }
366
367 out:
368 #if IS_ENABLED(CONFIG_UNICODE)
369 if (IS_CASEFOLDED(dir) && !de && use_hash &&
> 370 !sb_no_casefold_compat_fallback(inode->i_sb)) {
371 use_hash = false;
372 goto start_find_entry;
373 }
374 #endif
375 /* This is to increase the speed of f2fs_create */
376 if (!de)
377 F2FS_I(dir)->task = current;
378 return de;
379 }
380
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-28 10:07 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=202503281735.NGPfccfP-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuchao0@huawei.com \
/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.