From: Nathan Chancellor <nathan@kernel•org>
To: paulmck@kernel•org, aneesh.kumar@linux•ibm.com
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
sfr@canb•auug.org.au, elver@google•com, ndesaulniers@google•com,
clang-built-linux@googlegroups•com
Subject: Re: Build failure in -next
Date: Wed, 23 Jun 2021 16:41:53 -0700 [thread overview]
Message-ID: <5b55b544-67de-871d-465c-af3c8be203c3@kernel.org> (raw)
In-Reply-To: <20210623223015.GA315292@paulmck-ThinkPad-P17-Gen-1>
Hi Paul,
On 6/23/2021 3:30 PM, Paul E. McKenney wrote:
> Hello, Aneesh!
>
> Yesterday evening's next-20210622 testing gave me the following
> kernel-build error:
>
> ld: mm/mremap.o: in function `move_huge_pud':
> /home/git/linux-next/mm/mremap.c:372: undefined reference to `__compiletime_assert_395'
>
> Bisection landed on this commit:
>
> 257121c5aabe ("mm/mremap: convert huge PUD move to separate helper")
>
> I have no idea how this commit relates to that error message, but
> reverting this commit on top of next-20210622 really does get rid of
> the problem.
This was reported by Naresh Kamboju last week:
https://lore.kernel.org/r/CA+G9fYsWHE5Vu9T3FV-vtHHbVFJWEF=bmjQxwaZs3uVYef028g@mail.gmail.com/
It seems to be related to the fact that older versions of clang cannot
figure out that the HPAGE_PUD case in move_pgt_entry() is never called
when CONFIG_TRANSPARENT_HUGE is unset so it is not eliminated, which is
problematic because flush_pud_tlb_range() evaluates to BUILD_BUG() in
that case, which is called within move_huge_pud().
> The following reproducer provokes this error:
>
> tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --torture lock --configs LOCK07 --build-only --kconfig "CONFIG_DEBUG_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y" --kmake-arg "CC=clang-11"
>
> Run the above command in the top-level directory of your -next source
> tree, and using this compiler:
>
> $ clang-11 -v
> Ubuntu clang version 11.1.0-++20210428103817+1fdec59bffc1-1~exp1~20210428204431.166
> Target: x86_64-pc-linux-gnu
>
> Thoughts?
Aneesh had a patch in that thread above that would resolve the issue, it
just needs to be sent to Andrew for a fixup patch.
Cheers,
Nathan
prev parent reply other threads:[~2021-06-23 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 22:30 Build failure in -next Paul E. McKenney
2021-06-23 23:39 ` Nick Desaulniers
2021-06-24 0:19 ` Paul E. McKenney
2021-06-23 23:41 ` Nathan Chancellor [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=5b55b544-67de-871d-465c-af3c8be203c3@kernel.org \
--to=nathan@kernel$(echo .)org \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=clang-built-linux@googlegroups$(echo .)com \
--cc=elver@google$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ndesaulniers@google$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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