From: kernel test robot <lkp@intel.com>
To: "yohan.joung" <yohan.joung@sk.com>, jaegeuk@kernel.org, chao@kernel.org
Cc: llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
oe-kbuild-all@lists.linux.dev, pilhyun.kim@sk.com
Subject: Re: [f2fs-dev] [PATCH v4] f2fs: prevent the current section from being selected as a victim during GC
Date: Fri, 4 Apr 2025 00:23:57 +0800 [thread overview]
Message-ID: <202504032346.pFNGrse7-lkp@intel.com> (raw)
In-Reply-To: <20250403071016.2940-1-yohan.joung@sk.com>
Hi yohan.joung,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master v6.14 next-20250403]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/yohan-joung/f2fs-prevent-the-current-section-from-being-selected-as-a-victim-during-GC/20250403-151057
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20250403071016.2940-1-yohan.joung%40sk.com
patch subject: [PATCH v4] f2fs: prevent the current section from being selected as a victim during GC
config: i386-buildonly-randconfig-003-20250403 (https://download.01.org/0day-ci/archive/20250403/202504032346.pFNGrse7-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250403/202504032346.pFNGrse7-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/202504032346.pFNGrse7-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/f2fs/file.c:30:
>> fs/f2fs/segment.h:480:53: error: too few arguments provided to function-like macro invocation
480 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
| ^
fs/f2fs/segment.h:105:9: note: macro 'GET_SEC_FROM_SEG' defined here
105 | #define GET_SEC_FROM_SEG(sbi, segno) \
| ^
>> fs/f2fs/segment.h:480:9: error: use of undeclared identifier 'GET_SEC_FROM_SEG'
480 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
| ^
fs/f2fs/segment.h:483:53: error: too few arguments provided to function-like macro invocation
483 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
| ^
fs/f2fs/segment.h:105:9: note: macro 'GET_SEC_FROM_SEG' defined here
105 | #define GET_SEC_FROM_SEG(sbi, segno) \
| ^
fs/f2fs/segment.h:483:9: error: use of undeclared identifier 'GET_SEC_FROM_SEG'
483 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
| ^
4 errors generated.
vim +480 fs/f2fs/segment.h
458
459 static inline void __set_test_and_free(struct f2fs_sb_info *sbi,
460 unsigned int segno, bool inmem)
461 {
462 struct free_segmap_info *free_i = FREE_I(sbi);
463 unsigned int secno = GET_SEC_FROM_SEG(sbi, segno);
464 unsigned int start_segno = GET_SEG_FROM_SEC(sbi, secno);
465 unsigned int next;
466 unsigned int usable_segs = f2fs_usable_segs_in_sec(sbi);
467
468 spin_lock(&free_i->segmap_lock);
469 if (test_and_clear_bit(segno, free_i->free_segmap)) {
470 free_i->free_segments++;
471
472 if (!inmem && IS_CURSEC(sbi, secno))
473 goto skip_free;
474 next = find_next_bit(free_i->free_segmap,
475 start_segno + SEGS_PER_SEC(sbi), start_segno);
476 if (next >= start_segno + usable_segs) {
477 if (test_and_clear_bit(secno, free_i->free_secmap)) {
478 free_i->free_sections++;
479
> 480 if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
481 sbi->next_victim_seg[BG_GC] = NULL_SEGNO;
482
483 if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
484 sbi->next_victim_seg[FG_GC] = NULL_SEGNO;
485 }
486 }
487 }
488 skip_free:
489 spin_unlock(&free_i->segmap_lock);
490 }
491
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "yohan.joung" <yohan.joung@sk.com>, jaegeuk@kernel.org, chao@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, pilhyun.kim@sk.com,
yohan.joung@sk.com
Subject: Re: [PATCH v4] f2fs: prevent the current section from being selected as a victim during GC
Date: Fri, 4 Apr 2025 00:23:57 +0800 [thread overview]
Message-ID: <202504032346.pFNGrse7-lkp@intel.com> (raw)
In-Reply-To: <20250403071016.2940-1-yohan.joung@sk.com>
Hi yohan.joung,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master v6.14 next-20250403]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/yohan-joung/f2fs-prevent-the-current-section-from-being-selected-as-a-victim-during-GC/20250403-151057
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20250403071016.2940-1-yohan.joung%40sk.com
patch subject: [PATCH v4] f2fs: prevent the current section from being selected as a victim during GC
config: i386-buildonly-randconfig-003-20250403 (https://download.01.org/0day-ci/archive/20250403/202504032346.pFNGrse7-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250403/202504032346.pFNGrse7-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/202504032346.pFNGrse7-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/f2fs/file.c:30:
>> fs/f2fs/segment.h:480:53: error: too few arguments provided to function-like macro invocation
480 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
| ^
fs/f2fs/segment.h:105:9: note: macro 'GET_SEC_FROM_SEG' defined here
105 | #define GET_SEC_FROM_SEG(sbi, segno) \
| ^
>> fs/f2fs/segment.h:480:9: error: use of undeclared identifier 'GET_SEC_FROM_SEG'
480 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
| ^
fs/f2fs/segment.h:483:53: error: too few arguments provided to function-like macro invocation
483 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
| ^
fs/f2fs/segment.h:105:9: note: macro 'GET_SEC_FROM_SEG' defined here
105 | #define GET_SEC_FROM_SEG(sbi, segno) \
| ^
fs/f2fs/segment.h:483:9: error: use of undeclared identifier 'GET_SEC_FROM_SEG'
483 | if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
| ^
4 errors generated.
vim +480 fs/f2fs/segment.h
458
459 static inline void __set_test_and_free(struct f2fs_sb_info *sbi,
460 unsigned int segno, bool inmem)
461 {
462 struct free_segmap_info *free_i = FREE_I(sbi);
463 unsigned int secno = GET_SEC_FROM_SEG(sbi, segno);
464 unsigned int start_segno = GET_SEG_FROM_SEC(sbi, secno);
465 unsigned int next;
466 unsigned int usable_segs = f2fs_usable_segs_in_sec(sbi);
467
468 spin_lock(&free_i->segmap_lock);
469 if (test_and_clear_bit(segno, free_i->free_segmap)) {
470 free_i->free_segments++;
471
472 if (!inmem && IS_CURSEC(sbi, secno))
473 goto skip_free;
474 next = find_next_bit(free_i->free_segmap,
475 start_segno + SEGS_PER_SEC(sbi), start_segno);
476 if (next >= start_segno + usable_segs) {
477 if (test_and_clear_bit(secno, free_i->free_secmap)) {
478 free_i->free_sections++;
479
> 480 if (GET_SEC_FROM_SEG(sbi->next_victim_seg[BG_GC]) == secno)
481 sbi->next_victim_seg[BG_GC] = NULL_SEGNO;
482
483 if (GET_SEC_FROM_SEG(sbi->next_victim_seg[FG_GC]) == secno)
484 sbi->next_victim_seg[FG_GC] = NULL_SEGNO;
485 }
486 }
487 }
488 skip_free:
489 spin_unlock(&free_i->segmap_lock);
490 }
491
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-03 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 7:10 [f2fs-dev] [PATCH v4] f2fs: prevent the current section from being selected as a victim during GC yohan.joung
2025-04-03 7:10 ` yohan.joung
2025-04-03 7:19 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-04-03 7:19 ` Chao Yu
2025-04-03 15:11 ` [f2fs-dev] " kernel test robot
2025-04-03 15:11 ` kernel test robot
2025-04-03 16:23 ` kernel test robot [this message]
2025-04-03 16:23 ` kernel test robot
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=202504032346.pFNGrse7-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pilhyun.kim@sk.com \
--cc=yohan.joung@sk.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.