From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Nathan Chancellor <nathan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-next@vger.kernel.org, clang-built-linux@googlegroups.com,
lkft-triage@lists.linaro.org, linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>,
Arnd Bergmann <arnd@arndb.de>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] [clang] x86_64-linux-gnu-ld: mm/mremap.o: in function `move_pgt_entry': mremap.c:(.text+0x763): undefined reference to `__compiletime_assert_342'
Date: Fri, 18 Jun 2021 10:32:42 +0530 [thread overview]
Message-ID: <6f3c5317-2877-9a57-0126-e9305f000269@linux.ibm.com> (raw)
In-Reply-To: <YMuOSnJsL9qkxweY@archlinux-ax161>
On 6/17/21 11:32 PM, Nathan Chancellor wrote:
> Rebuilt the CC list because most people were added based on the
> incorrect bisect result.
>
> On Thu, Jun 17, 2021 at 02:51:49PM +0100, Matthew Wilcox wrote:
>> On Thu, Jun 17, 2021 at 06:15:45PM +0530, Naresh Kamboju wrote:
>>> On Thu, 17 Jun 2021 at 17:41, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>>>> x86_64-linux-gnu-ld: mm/mremap.o: in function `move_pgt_entry':
>>>> mremap.c:(.text+0x763): undefined reference to `__compiletime_assert_342'
>>>
>>> The git bisect pointed out the first bad commit.
>>>
>>> The first bad commit:
>>> commit 928cf6adc7d60c96eca760c05c1000cda061604e
>>> Author: Stephen Boyd <swboyd@chromium.org>
>>> Date: Thu Jun 17 15:21:35 2021 +1000
>>> module: add printk formats to add module build ID to stacktraces
>>
>> Your git bisect probably went astray. There's no way that commit
>> caused that regression.
>
> My bisect landed on commit 83f85ac75855 ("mm/mremap: convert huge PUD
> move to separate helper"). flush_pud_tlb_range() evaluates to
> BUILD_BUG() when CONFIG_TRANSPARENT_HUGEPAGE is unset but this function
> is present just based on the value of
> CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD.
>
> $ make -skj(nproc) ARCH=x86_64 CC=clang O=build/x86_64 distclean allnoconfig mm/mremap.o
>
> $ llvm-readelf -s build/x86_64/mm/mremap.o &| rg __compiletime_assert
> 21: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UND __compiletime_assert_337
>
> $ rg TRANSPARENT_ build/x86_64/.config
> 450:CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
> 451:CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD=y
> 562:# CONFIG_TRANSPARENT_HUGEPAGE is not set
>
> Not sure why this does not happen on newer clang versions, presumably
> something with inlining decisions? Still seems like a legitimate issue
> to me.
>
gcc 10 also doesn't give a build error. I guess that is because we evaluate
if (pud_trans_huge(*old_pud) || pud_devmap(*old_pud)) {
to if (0) with CONFIG_TRANSPARENT_HUGEPAGE disabled.
switching that to if (1) do results in BUILD_BUG triggering.
Should we fix this ?
modified mm/mremap.c
@@ -336,7 +336,7 @@ static inline bool move_normal_pud(struct
vm_area_struct *vma,
}
#endif
-#ifdef CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD
+#if defined(CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD) &&
defined(CONFIG_TRANSPARENT_HUGEPAGE)
static bool move_huge_pud(struct vm_area_struct *vma, unsigned long
old_addr,
unsigned long new_addr, pud_t *old_pud, pud_t *new_pud)
{
next prev parent reply other threads:[~2021-06-18 5:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 12:11 [next] [clang] x86_64-linux-gnu-ld: mm/mremap.o: in function `move_pgt_entry': mremap.c:(.text+0x763): undefined reference to `__compiletime_assert_342' Naresh Kamboju
2021-06-17 12:45 ` Naresh Kamboju
2021-06-17 13:51 ` Matthew Wilcox
2021-06-17 14:45 ` Naresh Kamboju
2021-06-17 15:07 ` Steven Rostedt
2021-06-17 15:13 ` Andy Shevchenko
2021-06-17 18:02 ` Nathan Chancellor
2021-06-18 5:02 ` Aneesh Kumar K.V [this message]
2021-06-18 23:05 ` Nathan Chancellor
2021-06-23 23:39 ` Nick Desaulniers
2021-06-24 0:18 ` Paul E. McKenney
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=6f3c5317-2877-9a57-0126-e9305f000269@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sfr@canb.auug.org.au \
--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