mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: yahia <yahia.a.abdrabou@gmail.com>, akpm@linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, david@kernel.org, ziy@nvidia.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	yahia <yahia.a.abdrabou@gmail.com>
Subject: Re: [PATCH] mm/migrate: Add native folio functions
Date: Mon, 8 Jun 2026 06:29:05 +0200	[thread overview]
Message-ID: <202606080649.AbjPE8ud-lkp@intel.com> (raw)
In-Reply-To: <20260608001251.66847-1-yahia.a.abdrabou@gmail.com>

Hi yahia,

kernel test robot noticed the following build errors:

[auto build test ERROR on akpm-mm/mm-everything]

url:    https://github.com/intel-lab-lkp/linux/commits/yahia/mm-migrate-Add-native-folio-functions/20260608-081741
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20260608001251.66847-1-yahia.a.abdrabou%40gmail.com
patch subject: [PATCH] mm/migrate: Add native folio functions
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260608/202606080649.AbjPE8ud-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260608/202606080649.AbjPE8ud-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/202606080649.AbjPE8ud-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from ./include/linux/bitmap.h:8,
                    from ./include/linux/cpumask.h:11,
                    from ./arch/x86/include/asm/paravirt.h:19,
                    from ./arch/x86/include/asm/irqflags.h:100,
                    from ./include/linux/irqflags.h:18,
                    from ./include/linux/spinlock.h:59,
                    from ./include/linux/swait.h:7,
                    from ./include/linux/completion.h:12,
                    from ./include/linux/crypto.h:15,
                    from arch/x86/kernel/asm-offsets.c:9:
   ./include/linux/page-flags.h: In function 'folio_test_MovableOpsIsolated':
>> ./include/linux/page-flags.h:412:19: error: 'PG_MovableOpsIsolated' undeclared (first use in this function); did you mean 'PG_movable_ops_isolated'?
     412 | { return test_bit(PG_##name, const_folio_flags(folio, page)); }
         |                   ^~~
   ./include/linux/bitops.h:43:32: note: in definition of macro 'bitop'
      43 |         ((__builtin_constant_p(nr) &&                                   \
         |                                ^~
   ./include/linux/page-flags.h:412:10: note: in expansion of macro 'test_bit'
     412 | { return test_bit(PG_##name, const_folio_flags(folio, page)); }
         |          ^~~~~~~~
   ./include/linux/page-flags.h:1113:1: note: in expansion of macro 'FOLIO_TEST_FLAG'
    1113 | FOLIO_TEST_FLAG(MovableOpsIsolated, movable_ops_isolated)
         | ^~~~~~~~~~~~~~~
   ./include/linux/page-flags.h:412:19: note: each undeclared identifier is reported only once for each function it appears in
     412 | { return test_bit(PG_##name, const_folio_flags(folio, page)); }
         |                   ^~~
   ./include/linux/bitops.h:43:32: note: in definition of macro 'bitop'
      43 |         ((__builtin_constant_p(nr) &&                                   \
         |                                ^~
   ./include/linux/page-flags.h:412:10: note: in expansion of macro 'test_bit'
     412 | { return test_bit(PG_##name, const_folio_flags(folio, page)); }
         |          ^~~~~~~~
   ./include/linux/page-flags.h:1113:1: note: in expansion of macro 'FOLIO_TEST_FLAG'
    1113 | FOLIO_TEST_FLAG(MovableOpsIsolated, movable_ops_isolated)
         | ^~~~~~~~~~~~~~~
>> ./include/linux/page-flags.h:1113:37: error: 'movable_ops_isolated' undeclared (first use in this function); did you mean 'PG_movable_ops_isolated'?
    1113 | FOLIO_TEST_FLAG(MovableOpsIsolated, movable_ops_isolated)
         |                                     ^~~~~~~~~~~~~~~~~~~~
   ./include/linux/bitops.h:44:44: note: in definition of macro 'bitop'
      44 |           __builtin_constant_p((uintptr_t)(addr) != (uintptr_t)NULL) && \
         |                                            ^~~~
   ./include/linux/page-flags.h:412:10: note: in expansion of macro 'test_bit'
     412 | { return test_bit(PG_##name, const_folio_flags(folio, page)); }
         |          ^~~~~~~~
   ./include/linux/page-flags.h:1113:1: note: in expansion of macro 'FOLIO_TEST_FLAG'
    1113 | FOLIO_TEST_FLAG(MovableOpsIsolated, movable_ops_isolated)
         | ^~~~~~~~~~~~~~~


vim +412 ./include/linux/page-flags.h

dfbac6dc68bae9 Matthew Wilcox (Oracle  2024-02-27  406) 
f94a62e910840b Christoph Lameter       2008-04-28  407  /*
f94a62e910840b Christoph Lameter       2008-04-28  408   * Macros to create function definitions for page flags
f94a62e910840b Christoph Lameter       2008-04-28  409   */
dfbac6dc68bae9 Matthew Wilcox (Oracle  2024-02-27  410) #define FOLIO_TEST_FLAG(name, page)					\
ce3467af6bded1 Matthew Wilcox (Oracle  2024-02-27  411) static __always_inline bool folio_test_##name(const struct folio *folio) \
ce3467af6bded1 Matthew Wilcox (Oracle  2024-02-27 @412) { return test_bit(PG_##name, const_folio_flags(folio, page)); }
dfbac6dc68bae9 Matthew Wilcox (Oracle  2024-02-27  413) 

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      parent reply	other threads:[~2026-06-08  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08  0:12 yahia
2026-06-08  0:29 ` Zi Yan
2026-06-08 16:46   ` David Hildenbrand (Arm)
2026-06-08  3:18 ` kernel test robot
2026-06-08  4:29 ` kernel test robot [this message]

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=202606080649.AbjPE8ud-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yahia.a.abdrabou@gmail.com \
    --cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox