From: kernel test robot <lkp@intel.com>
To: Junjie Fu <fujunjie1@qq.com>,
linux-mm@kvack.org, akpm@linux-foundation.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, willy@infradead.org, sj@kernel.org,
Junjie Fu <fujunjie1@qq.com>
Subject: Re: [PATCH RESEND] mempolicy.h: Remove unnecessary header file inclusions with no test failure
Date: Thu, 12 Dec 2024 01:18:31 +0800 [thread overview]
Message-ID: <202412120124.VtMN4Kk6-lkp@intel.com> (raw)
In-Reply-To: <tencent_C12D22B8989E0314FDE7073D6446186E3C09@qq.com>
Hi Junjie,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on brauner-vfs/vfs.all linus/master v6.13-rc2 next-20241211]
[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/Junjie-Fu/mempolicy-h-Remove-unnecessary-header-file-inclusions-with-no-test-failure/20241211-120550
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/tencent_C12D22B8989E0314FDE7073D6446186E3C09%40qq.com
patch subject: [PATCH RESEND] mempolicy.h: Remove unnecessary header file inclusions with no test failure
config: i386-buildonly-randconfig-003-20241211 (https://download.01.org/0day-ci/archive/20241212/202412120124.VtMN4Kk6-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241212/202412120124.VtMN4Kk6-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/202412120124.VtMN4Kk6-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/z3fold.c:30:
In file included from include/linux/mm.h:2287:
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_"
| ~~~~~~~~~~~ ^ ~~~
>> mm/z3fold.c:353:3: error: call to undeclared function 'lock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
353 | lock_page(page);
| ^
mm/z3fold.c:353:3: note: did you mean 'copy_page'?
arch/x86/include/asm/page_32.h:25:20: note: 'copy_page' declared here
25 | static inline void copy_page(void *to, void *from)
| ^
>> mm/z3fold.c:355:3: error: call to undeclared function 'unlock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
355 | unlock_page(page);
| ^
mm/z3fold.c:1052:3: error: call to undeclared function 'lock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1052 | lock_page(page);
| ^
mm/z3fold.c:1054:3: error: call to undeclared function 'unlock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1054 | unlock_page(page);
| ^
>> mm/z3fold.c:1056:12: error: call to undeclared function 'trylock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1056 | WARN_ON(!trylock_page(page));
| ^
mm/z3fold.c:1056:12: note: did you mean 'try_get_page'?
include/linux/mm.h:1527:33: note: 'try_get_page' declared here
1527 | static inline __must_check bool try_get_page(struct page *page)
| ^
mm/z3fold.c:1058:3: error: call to undeclared function 'unlock_page'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
1058 | unlock_page(page);
| ^
1 warning and 6 errors generated.
vim +/lock_page +353 mm/z3fold.c
9a001fc19cccdeb Vitaly Wool 2016-05-20 348
9a001fc19cccdeb Vitaly Wool 2016-05-20 349 /* Resets the struct page fields and frees the page */
1f862989b04ade6 Vitaly Wool 2019-05-13 350 static void free_z3fold_page(struct page *page, bool headless)
9a001fc19cccdeb Vitaly Wool 2016-05-20 351 {
1f862989b04ade6 Vitaly Wool 2019-05-13 352 if (!headless) {
1f862989b04ade6 Vitaly Wool 2019-05-13 @353 lock_page(page);
1f862989b04ade6 Vitaly Wool 2019-05-13 354 __ClearPageMovable(page);
1f862989b04ade6 Vitaly Wool 2019-05-13 @355 unlock_page(page);
1f862989b04ade6 Vitaly Wool 2019-05-13 356 }
5a27aa8220290b6 Vitaly Wool 2017-02-24 357 __free_page(page);
5a27aa8220290b6 Vitaly Wool 2017-02-24 358 }
5a27aa8220290b6 Vitaly Wool 2017-02-24 359
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-12-11 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 4:01 Junjie Fu
2024-12-11 17:18 ` kernel test robot [this message]
2024-12-12 0:21 ` 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=202412120124.VtMN4Kk6-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=fujunjie1@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@kernel.org \
--cc=willy@infradead.org \
/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