From: "Arnd Bergmann" <arnd@arndb.de>
To: "James Houghton" <jthoughton@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: "kernel test robot" <lkp@intel.com>,
linux-mm@kvack.org, oe-kbuild-all@lists.linux.dev,
"Yu Zhao" <yuzhao@google.com>
Subject: Re: [linux-next:pending-fixes 301/373] mm/vmscan.c:3498: undefined reference to `pmdp_test_and_clear_young'
Date: Wed, 30 Oct 2024 11:28:18 +0000 [thread overview]
Message-ID: <25faaaf4-d2c3-4dc0-86d4-55dd25568c12@app.fastmail.com> (raw)
In-Reply-To: <20241025192106.957236-1-jthoughton@google.com>
On Fri, Oct 25, 2024, at 19:21, James Houghton wrote:
> Hi Andrew,
>
> The following diff applied to the second patch[1] fixes this error. The
> diff is functionally a no-op; the get_pmd_pfn() immediately following
> the code here would return -1 in the !pmd_present() case.
>
> I can send a brand new patch if you'd prefer.
>
> [1]:
> https://lore.kernel.org/linux-mm/20241019012940.3656292-3-jthoughton@google.com/
I ran into another problem with the build failure below, and found
that your fixup address this as well.
Arnd
In file included from <command-line>:
In function 'pmdp_test_and_clear_young',
inlined from 'walk_pmd_range_locked.constprop.isra' at mm/vmscan.c:3504:8:
include/linux/compiler_types.h:517:45: error: call to '__compiletime_assert_401' declared with attribute error: BUILD_BUG failed
517 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
include/linux/compiler_types.h:498:25: note: in definition of macro '__compiletime_assert'
498 | prefix ## suffix(); \
| ^~~~~~
include/linux/compiler_types.h:517:9: note: in expansion of macro '_compiletime_assert'
517 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:39:37: note: in expansion of macro 'compiletime_assert'
39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
include/linux/build_bug.h:59:21: note: in expansion of macro 'BUILD_BUG_ON_MSG'
59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
| ^~~~~~~~~~~~~~~~
include/linux/pgtable.h:383:9: note: in expansion of macro 'BUILD_BUG'
383 | BUILD_BUG();
| ^~~~~~~~~
prev parent reply other threads:[~2024-10-30 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 13:12 kernel test robot
2024-10-25 19:21 ` James Houghton
2024-10-30 11:28 ` Arnd Bergmann [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=25faaaf4-d2c3-4dc0-86d4-55dd25568c12@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=jthoughton@google.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuzhao@google.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