All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org,
	riel@surriel.com, liam@infradead.org, vbabka@kernel.org,
	harry@kernel.org, jannh@google.com, sj@kernel.org,
	ziy@nvidia.com, balbirs@nvidia.com,
	oe-kbuild-all@lists.linux.dev, linux-mm@kvack.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] mm/page_vma_mapped: revalidate and do proper check before return device-private pmd
Date: Wed, 24 Jun 2026 03:13:47 +0000	[thread overview]
Message-ID: <20260624031347.zq2lhnnthuxqcuql@master> (raw)
In-Reply-To: <202606240042.ffPsEXVc-lkp@intel.com>

On Wed, Jun 24, 2026 at 12:18:20AM +0800, kernel test robot wrote:
>Hi Wei,
>
>kernel test robot noticed the following build errors:
>

Thanks for reporting.

>[auto build test ERROR on akpm-mm/mm-everything]
>
>url:    https://github.com/intel-lab-lkp/linux/commits/Wei-Yang/mm-page_vma_mapped-revalidate-and-do-proper-check-before-return-device-private-pmd/20260623-012838
>base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
>patch link:    https://lore.kernel.org/r/20260622130651.23359-1-richard.weiyang%40gmail.com
>patch subject: [PATCH] mm/page_vma_mapped: revalidate and do proper check before return device-private pmd
>config: parisc-randconfig-002-20260623 (https://download.01.org/0day-ci/archive/20260624/202606240042.ffPsEXVc-lkp@intel.com/config)

So this is parisc arch.

In the config file, HAVE_ARCH_TRANSPARENT_HUGEPAGE is not defined. Which leads
to !TRANSPARENT_HUGEPAGE and !PGTABLE_HAS_HUGE_LEAVES.

And then trigger the BUILD_BUG().

>compiler: hppa-linux-gcc (GCC) 8.5.0
>reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260624/202606240042.ffPsEXVc-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/202606240042.ffPsEXVc-lkp@intel.com/
>
>All errors (new ones prefixed by >>):
>
>   In file included from <command-line>:
>   In function 'check_pmd.isra.24',
>       inlined from 'page_vma_mapped_walk' at mm/page_vma_mapped.c:283:11:
>>> include/linux/compiler_types.h:699:38: error: call to '__compiletime_assert_406' declared with attribute error: BUILD_BUG failed
>     _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>                                         ^
>   include/linux/compiler_types.h:680:4: note: in definition of macro '__compiletime_assert'
>       prefix ## suffix();    \
>       ^~~~~~
>   include/linux/compiler_types.h:699:2: note: in expansion of macro '_compiletime_assert'
>     _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>     ^~~~~~~~~~~~~~~~~~~
>   include/linux/build_bug.h:40:37: note: in expansion of macro 'compiletime_assert'
>    #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
>                                        ^~~~~~~~~~~~~~~~~~
>   include/linux/build_bug.h:60:21: note: in expansion of macro 'BUILD_BUG_ON_MSG'
>    #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
>                        ^~~~~~~~~~~~~~~~
>   include/linux/huge_mm.h:113:28: note: in expansion of macro 'BUILD_BUG'
>    #define HPAGE_PMD_SHIFT ({ BUILD_BUG(); 0; })
>                               ^~~~~~~~~
>   include/linux/huge_mm.h:117:26: note: in expansion of macro 'HPAGE_PMD_SHIFT'
>    #define HPAGE_PMD_ORDER (HPAGE_PMD_SHIFT-PAGE_SHIFT)
>                             ^~~~~~~~~~~~~~~
>   include/linux/huge_mm.h:118:26: note: in expansion of macro 'HPAGE_PMD_ORDER'
>    #define HPAGE_PMD_NR (1<<HPAGE_PMD_ORDER)
>                             ^~~~~~~~~~~~~~~
>   mm/page_vma_mapped.c:142:13: note: in expansion of macro 'HPAGE_PMD_NR'
>     if ((pfn + HPAGE_PMD_NR - 1) < pvmw->pfn)
>                ^~~~~~~~~~~~
>

This is in definition of check_pmd() which is already in kernel for a while.

I will update current version, and take a look to how to fix it.

>
>vim +/__compiletime_assert_406 +699 include/linux/compiler_types.h
>
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  685  
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  686  #define _compiletime_assert(condition, msg, prefix, suffix) \
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  687  	__compiletime_assert(condition, msg, prefix, suffix)
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  688  
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  689  /**
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  690   * compiletime_assert - break build and emit msg if condition is false
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  691   * @condition: a compile-time constant condition to check
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  692   * @msg:       a message to emit if condition is false
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  693   *
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  694   * In tradition of POSIX assert, this macro will break the build if the
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  695   * supplied condition is *false*, emitting the supplied error message if the
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  696   * compiler has support to do so.
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  697   */
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  698  #define compiletime_assert(condition, msg) \
>eb5c2d4b45e3d2d Will Deacon 2020-07-21 @699  	_compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>eb5c2d4b45e3d2d Will Deacon 2020-07-21  700  
>
>--
>0-DAY CI Kernel Test Service
>https://github.com/intel/lkp-tests/wiki

-- 
Wei Yang
Help you, Help me

  reply	other threads:[~2026-06-24  3:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 13:06 [PATCH] mm/page_vma_mapped: revalidate and do proper check before return device-private pmd Wei Yang
2026-06-22 13:14 ` Wei Yang
2026-06-22 13:46 ` Lorenzo Stoakes
2026-06-22 14:21   ` Wei Yang
2026-06-22 14:59     ` Lance Yang
2026-06-22 16:11     ` Lorenzo Stoakes
2026-06-22 23:45       ` Wei Yang
2026-06-23 17:02         ` Lorenzo Stoakes
2026-06-24  2:09           ` Wei Yang
2026-06-22 14:44   ` Lance Yang
2026-06-23 16:18 ` kernel test robot
2026-06-24  3:13   ` Wei Yang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-08  1:37 Wei Yang
2026-05-08 21:51 ` Andrew Morton
2026-05-10  1:22   ` Wei Yang
2026-05-08 22:48 ` Balbir Singh
2026-05-10  1:20   ` Wei Yang
2026-05-12 12:43   ` David Hildenbrand (Arm)
2026-05-12 14:35     ` Wei Yang
2026-05-12 18:55       ` David Hildenbrand (Arm)
2026-05-12 23:03         ` Balbir Singh
2026-05-12 23:14           ` Wei Yang
2026-05-12 23:19             ` Balbir Singh
2026-05-13  1:47             ` Balbir Singh
2026-06-12  2:48         ` Wei Yang
2026-06-15 11:58           ` David Hildenbrand (Arm)

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=20260624031347.zq2lhnnthuxqcuql@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbirs@nvidia.com \
    --cc=david@kernel.org \
    --cc=harry@kernel.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=riel@surriel.com \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@kernel.org \
    --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 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.