From: Peter Xu <peterx@redhat.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@nvidia.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: mm/gup.c:679:22: error: call to '__compiletime_assert_382' declared with 'error' attribute: BUILD_BUG failed
Date: Thu, 4 Apr 2024 07:57:12 -0400 [thread overview]
Message-ID: <Zg6VmKwT6ts2_pVM@x1n> (raw)
In-Reply-To: <CANiq72mVuYbOKmjFUXf5eTeS8a3RoruZfyYvw+_iN+tkd9HzSg@mail.gmail.com>
On Thu, Apr 04, 2024 at 12:42:12PM +0200, Miguel Ojeda wrote:
> Hi Peter, Andrew,
Hi, Miguel,
>
> I am not sure if this is one of the issues that Peter mentioned [1] to
> be resolved or not eventually, but I have spotted this in the last
> couple -next runs for a LLVM=1 loongarch64 defconfig build [2].
It's the one reported after that:
https://lore.kernel.org/r/20240402190549.GA706730@dev-arch.thelio-3990X
Please try this:
https://lore.kernel.org/r/20240403013249.1418299-4-peterx@redhat.com
It's already included in Andrew's latest mm-unstable, commit 8c9a7c14a7d4.
I don't know how fast it spreads to -next, but assume it'll get there soon
too.
Sorry for the issue!
>
> Hope that helps!
>
> Cheers,
> Miguel
>
> [1] https://lore.kernel.org/all/ZgMzaMu7oILiNLcG@x1n/
> [2]
>
> mm/gup.c:679:22: error: call to '__compiletime_assert_382' declared
> with 'error' attribute: BUILD_BUG failed
> 679 | unsigned long pfn = pud_pfn(pud);
> | ^
> ./include/linux/pgtable.h:1887:23: note: expanded from macro 'pud_pfn'
> 1887 | #define pud_pfn(x) ({ BUILD_BUG(); 0; })
> | ^
> ./include/linux/build_bug.h:59:21: note: expanded from macro 'BUILD_BUG'
> 59 | #define BUILD_BUG() BUILD_BUG_ON_MSG(1, "BUILD_BUG failed")
> | ^
> ./include/linux/build_bug.h:39:37: note: expanded from macro 'BUILD_BUG_ON_MSG'
> 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
> | ^
> note: (skipping 1 expansions in backtrace; use
> -fmacro-backtrace-limit=0 to see all)
> ././include/linux/compiler_types.h:448:2: note: expanded from macro
> '_compiletime_assert'
> 448 | __compiletime_assert(condition, msg, prefix, suffix)
> | ^
> ././include/linux/compiler_types.h:441:4: note: expanded from macro
> '__compiletime_assert'
> 441 | prefix ## suffix(); \
> | ^
> <scratch space>:48:1: note: expanded from here
> 48 | __compiletime_assert_382
> | ^
> 1 error generated.
>
--
Peter Xu
next prev parent reply other threads:[~2024-04-04 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:42 mm/gup.c:679:22: error: call to '__compiletime_assert_382' declared with 'error' attribute: BUILD_BUG failed Miguel Ojeda
2024-04-04 11:57 ` Peter Xu [this message]
2024-04-05 13:21 ` Miguel Ojeda
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=Zg6VmKwT6ts2_pVM@x1n \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=miguel.ojeda.sandonis@gmail.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.